Any AM, SM, or CMP overload conditions are shown on the 109
     display page. The SM and CMP overload information is provided on
     a summary basis.  If an SM overload occurs, the SM number and
     type will be displayed in the indicator and backlighted. If more
     than 16 SMs are in overload, a note will appear, partially
     backlighted, indicating how many SMs are overloaded.  For a
     complete list of SMs in overload, the 900 command should be
     entered.  If a CMP overload occurs, the CMP number and whether
     it is the primary (P) or mate (M) is shown.

     Details on an SM overload can be obtained by entering the
     DISPLAY SM X OVERLOAD INFO command shown on the display.
     Likewise, details on an overloaded CMP can be obtained by
     entering the DISPLAY PRIM CMP X OVERLOAD INFO or DISPLAY MATE
     CMP X OVERLOAD INFO.

     The REALTIME overload indicators will contain NONE, MINOR,
     MAJOR, or CRIT to show the severity of the overload. NONE means
     no overload exists. MINOR and MAJOR are different levels of
     real-time overloads. CRIT (critical) is only used for SMs and is
     the most severe type of overload.

     The only craft action which can be taken during overload
     conditions is to reduce or eliminate input messages/maintenance
     commands. All other actions are initiated by the system.

     For RESOURCE overloads, either NONE or the name of the resource
     will be displayed. The monitored resources are as follows:

       o  MCB - Message Control Block

       o  PCB - Process Control Block

       o  RC/V - Tone Receivers (SM only)

       o  SCB - Stack Control Block

       o  TCB - Timer Control Block

       o  PKB - Packet Buffers [operator services position system
          (OSPS) SMs only]

       o  PSU - Packet Switch Unit (Packet Switching SMs only)

       o  ADB - Analog Data Block (SM only)

       o  APB - Associated Process Block (SM only)

       o  BRCSDB - Business and Residence Custom Services (BRCS) Data
          Block (SM only)

       o  CBDB - Call Buildup Data Block (SM only)

       o  CCBCOM - Channel Control Block (SM only)

       o  CHDB - Channel Data Block (SM only)

       o  CLDB - Calling Leg Data Block (SM only)

       o  DALB - D-Channel Application Linkage Block (SM only)

       o  DIB - Data Interface Block (SM only)

       o  DISPDB - Display Data Block (SM only)

       o  E911DB - Enhanced 911 Data Block (SM only)

       o  MDB - Model Data Block (SM only)

       o  MSG - Message Overflow (because of PIC overload)

       o  PHDB - Path Data Block (SM only)

       o  SCMDB - Shared Call Model Data Block (SM only)

       o  TSDB - Time Slot Data Block (SM only)

       o  PSIB - X-25 Packet Input Buffer (SM only)

       o  IAQ - CMP Input Queue (CMP only).

     Essential Service Protection is normally inhibited. Therefore,
     the INHIBITED text is not backlighted. When allowed, it gives
     preferential treatment to designated lines (for example,
     hospitals, police, fire departments, etc.) during periods of
     overload.

     If there is a network management control on, to prevent
     overloads in this office, the ``SEE PAGE 130'' indicator will
     show up and be backlighted.

     An overload will cause the OVERLOAD indicator at the top of the
     screen to backlight. The associated alarm level (CRITICAL,
     MAJOR, or MINOR) will also backlight, if applicable.

     The AM information box contains information regarding real-time
     and resource overloads in the AM.

     The information provided on Page 109 for the SMs is the SM
     number and type.  For additional information on a specific SM,
     the poke 1300,X is used (where X is the number of the SM).

     Figure .AW G285/ shows an example of the 109 display page with
     specific AM overload information. It also shows up to 16 of the
     SMs and up to 8 of the CMPs that are in overload. The note
     EXCESSIVE is displayed and backlighted because there are greater
     than 16 SMs in overload. The actual number of SMs in overload
     (20) is displayed.

     The SM overload information shows an overload for resource
     E911DB, Enhanced 911 Data Block, a new resource for 5E7.

     Similar to the SM, the CMP has limited information provided on
     Page 109 as shown in Figure .AW G286/.  The information shown is the
     number of the CMP and whether the CMP is the primary or the
     mate.  For more specific information regarding a specific CMP,
     pokes 1370,X for the primary CMP and 1371,X for the mate CMP
     (where X is the number of the CMP) are used.

     Commands are provided to inhibit and allow ESP, to output a list
     of all SMs that are overloaded, and to obtain detailed
     information on an SM overload condition.

     In addition to these commands, any available paging command can
     be entered from Display Page 109.

      CMD     RESULT

      600     Essential Service Protection is inhibited (INH:ESP)
      700     Essential Service Protection is allowed (ALW:ESP)
      900     Output list of SMs in overload on the ROP (OP:OVRLD:ALL)
     1300,X   SM X Overload Information is displayed
     1370,X   Primary CMP X overload information is displayed
     1371,X   Mate CMP X overload information is displayed

     The 110 display page provides a list of system and AM inhibits
     and provides maintenance menu commands for selected inhibits.
     A SYSTEM inhibit applies to the AM and all SMs.  An AM inhibit
     applies only to the AM. Unless stated otherwise, all inhibit
     requests are assumed to be phase-protected.

     Each inhibit indicator on this display has three distinct
     sections: the top line, the description, and the commands-
     available line.

     The top line in each box shows the box number. This line is
     displayed in normal video and the field to the right of the box
     number is blank unless an inhibit has been requested by the
     craft. If an inhibit has been requested, INH, SET, MON, or CHG
     is displayed to the right of the box number, as appropriate, and
     the top line is backlighted. (For the remainder of the 110
     display page description, the result of any of these operations
     is referred to as an inhibit.) The presence of this text and
     backlighting combination means the system has recorded the
     inhibit request. It does not mean the inhibit is in effect.

     Most of the inhibit/allow and set/clear commands are effective
     immediately after the request. For these cases, all areas of the
     indicator backlight together and one of the 3-character phrases
     (INH, SET, MON, or CHG) will appear.  However, in a few cases,
     the status will change independent of the request. An example of
     this is shown in box 21. The behavior of each indicator is
     explained in the Indicators section on the next several pages.

     The middle two lines of the indicator is the inhibit
     description. These two lines show the name of the inhibit as
     well as whether or not an inhibit is in effect. Inhibits can be
     caused by system or craft-initiated actions. When an inhibit is
     in effect, this section will be backlighted. In the SUMMARY
     STATUS AREA, the SYS INH indicator will be backlighted.

     The return of the top line to normal video means that a valid
     request to allow (or clear) an inhibit has been accepted. A
     valid allow request will also cause any text in the area to the
     right of the box number to be blanked.

     The last line of each indicator shows which menu commands, if
     any, are available from the display. For example, at the bottom
     of box 17 the numbers ``6 7 9'' appear. The ``6'' means this
     item can be inhibited by entering  617, the ``7'' means it can
     be allowed by entering  717, and the ``9'' designates output is
     available with  917. On color MCCs, there is also color mapping
     from the commands shown on the left of the display to the
     numbers in the boxes. Boxes without commands listed are
     inhibited only by the system or from manual action independent
     of this display page.

     Following is the correspondence between the number key and the
     action taken:

        Number   Action

          4      Set
          5      Clear
          6      Inhibit
          7      Allow
          9      Output

     This paragraph describes the individual indicators and their
     behavior.

     Box 00 - Box 00 is not currently used.

     Box 01 - Message Class Brevity Control

     This indicator shows whether or not the automatic output message
     class brevity control is inhibited. Brevity control is used to
     restrict the generation of certain application output messages
     for both the AM and equipped SMs. Inhibiting message class
     brevity control permits normally suppressed messages to go to
     the ROP or the log file.

     The message class brevity control inhibit must be entered with
     the teletypewriter (TTY) input message INH:BREVC,MSGCLS=a.
     Since a named MSGCLS is required, a menu command is not
     provided.  Inhibiting brevity control for one or more MSGCLSs
     may cause increased communication link traffic which can degrade
     call processing performance and capacity. (See AT&T 235-600-700,
     Input Messages Manual.) The request will display INH when
     recorded.  This inhibit will take effect immediately with the
     request.

     Entering allow command 701 generates the message
     ALW:BREVC,MSGCLS=ALL. The request will clear the text INH when
     recorded. This allow will take effect immediately with the
     request.

     This inhibit is cleared by any high-level AM initialization.

     Box 02 - Message Class Log/Print Status

     The box 02 indicates that at least one message class has the
     log/print status that is different from the backup status.

     To change the log/print status for one or all message classes,
     enter input message CHG:LPS,MSGCLS={a|ALL} with additional
     parameters.  (See AT&T 235-600-700, Input Messages Manual.)  The
     request will display CHG when recorded. This change will take
     effect immediately with the request.

     Entering the menu command 902 generates the input message
     OP:LPS,MSGCLS=ALL and causes the status of the message classes
     to be printed at the ROP.

     Box 03 - MDII Reporting

     The machine-detected interoffice irregularity (MDII) indicator
     is backlighted when one or more MDIIs are inhibited. The
     inhibits are generated by the TTY input message INH:MDII with
     additional parameters. When the inhibit is invoked, it
     suppresses the printing of MDIIs for the trunk group(s)
     specified by the input message. The request will display INH
     when recorded. This inhibit will take effect immediately with
     the request.

     Entering the 903 command generates the message OP:MDII, which
     causes a listing of all suppressed trunk MDIIs to be printed at
     the ROP.

     Box 04 - Manual Recent Change

     This indicator shows whether or not manual entering of recent
     changes is inhibited.

     When the command 604 is entered, the message INH:RC is
     generated. The request will display INH when recorded. This
     inhibit will take effect immediately with the request.

     The allow command 704 generates the message ALW:RC. The request
     will clear the text INH when recorded.

     Since the Automatic Customer Station Rearrangement (ACSR)
     feature depends upon Recent Change, if Recent Change is
     inhibited, ACSR is also inhibited.  During manual inhibits of
     Recent Change, the RC box (box 04) is illuminated and the CORC
     box (box 05) is partially illuminated.

     Box 05 - Customer-Originated Recent Change (CORC)

     The box 05 indicator shows whether CORCs are inhibited.

     Box 05 is shared by CORCs and the ACSR feature.  Since the ACSR
     feature depends upon Recent Change, if Recent Change is
     inhibited, ACSR is also inhibited.  During manual inhibits of
     Recent Change, the RC box (box 04) is illuminated and the CORC
     box (box 05) is partially illuminated.

     When a 905 command is entered, ACSR queuing is inhibited and
     CORCs are allowed.

     Box 06 - Recent Change Logging

     The box 06 indicator shows whether or not the logging of
     manually entered recent changes for all processors is inhibited.
     This does not include customer-originated recent changes. Recent
     Change logging may be inhibited in the event logging is causing
     a problem, thereby allowing recent changes to be entered.
     Unlogged changes are lost after a boot.

     Entering the command 606 generates the message INH:RCLOG. The
     request will display INH when recorded. This inhibit will take
     effect immediately with the request.

     Entering the command 706 generates the message ALW:RCLOG. The
     request will clear the text INH when recorded.

     Box 07 - Box 7 is not currently used.

     Box 08 - Communication Link Normalization

     If a fault occurs in one or more SM communication links, the
     system will automatically try to restore the link(s) on a
     periodic basis. This inhibit will suppress this action when
     active.

     Entering command 608 will generate the message INH:CLNORM. The
     request will display INH when recorded. This inhibit will take
     effect immediately with the request.

     When the command 708 is entered, it generates the message
     ALW:CLNORM. The request will clear the text INH when recorded.

     Since attempts to restore CLNKS are periodic, there may be a
     delay from the time an allow or inhibit request is recorded
     until the allow or inhibit is recognized.

     Box 09 - Centralized Automatic Message Accounting (CAMA)
     Suspension

     The box 09 indicator shows whether or not calls are being routed
     through the CAMA operator number identification (ONI) process
     for billing.  Since inhibiting this indicator causes lost
     revenue, a minor alarm is sounded when the inhibit is invoked.

     Entering the command 609 generates the message INH:CAMAONI. The
     request will display INH when recorded. This inhibit will take
     effect immediately with the request.

     Entering the command 709 generates the message ALW:CAMAONI. The
     request will clear the text INH when recorded.

     Box 10 - Trunk Hold

     The box 10 indicator shows whether or not one or more trunk
     groups are being monitored.

     To monitor one or more trunk groups, the input message MON:TRUNK
     must be entered. The request will display MON when recorded.
     This monitoring will take effect immediately with the request.

     The system looks for stop-go signaling failures in members of
     monitored group(s). If a failure occurs, the member is held
     off-hook and out of service for the craft to determine the
     nature of the failure.

     The input message CLR:TRUNK is entered to remove the stop-go
     signaling.

       Warning:   This message will return all members back to
                  service, even if they failed.  The request will
                  clear the text MON when recorded.

     Entering the 910 command generates the input message OP:TRUNK,
     which causes a listing of all trunk groups and members being
     monitored to be printed at the ROP.

     Boxes 11 Through 15 -  Boxes 11 through 15 are not currently
     used.

     Box 16 - Routine Audits

     The box 16 indicator shows if the automatic routine execution of
     one or both AM application audit cycles (OKP or SMKP) are
     inhibited.

     The only way to obtain a single audit inhibit is via a TTY input
     message in the message mode. (See INH:AUD=a,ENV=b in AT&T 235-
     600-700, Input Messages Manual.) Single inhibits are not phase
     protected.

     Entering the 616 command requests the inhibit of all audits and
     generates the message INH:AUD=CYCLE,ENV. The request will
     display INH when recorded. The request state does not
     necessarily imply that the inhibit is in effect. Normally, the
     status will follow the request within a short period of time.

     If the 716 command is entered, the message ALW:AUD=CYCLE,ENV is
     sent. The request will clear the text INH when recorded. The
     request state does not necessarily imply that the inhibit has
     been cleared. Normally, the status will follow the request
     within a short period of time.

     The command 916 (OP:AUD,STATUS=ALL,ENV=a) can be entered to get
     the ROP listing of routine audit status for the application AM.

     Box 17 - Routine Exercises

     The box 17 indicator shows if any or all of the application
     routine hardware exercises are inhibited in the communication
     module (CM).  Inhibits for routine exercises are effective for
     only one exercise session. If the tests are in progress when the
     message is received, the inhibit will not take place until the
     next session.

     Routine exercises are scheduled to run at specific times (for
     example, daily at midnight). If inhibited exercises are allowed
     after the scheduled time, the exercises are not started until
     the next scheduled session.

     When 617 is entered, the message INH:REX,CM is generated, which
     inhibits all application CM routine exercises. The request will
     display INH when recorded. This inhibit will take effect
     immediately with the request.

     If the command 717 is entered, the message ALW:REX,CM is
     generated, which allows all application CM routine exercises.
     The request will clear the text INH when recorded.

     Entering the command 917 sends the message OP:REXINH,CM, which
     generates a status listing at the ROP.

       Note:   These are application routine exercises and are
               different from the routine exercises for the AM, as
               shown on the EAI display.

     Box 18 - Software Checks

     The box 18 indicator reflects whether or not the AM application
     software checks have been inhibited. The AM software checks and
     the application software checks are different, but are
     controlled together from manual commands.

     The box 18 indicator can only be controlled from the EAI or TTY
     input message INH:SFTCHK.  This inhibit will prevent internal
     software checks from causing initializations.

     Entering the 618 command requests the inhibit of internal
     software checks and generates the message INH:SFTCHK.  The
     request will display INH when recorded.  The request state does
     not necessarily imply that  the inhibit is in effect.  Normally
     the status will follow the request within a short period of
     time.

     If the status is inhibited without being requested, the inhibit
     was automatically applied by the system.

     If the 718 command is entered, the message ALW:SFTCHK is sent.
     The request will clear the text INH when recorded.

     Box 19 - Min-Mode

     The box 19 indicator shows the states of application min-mode.
     When this box is backlighted, no call processing functions are
     allowed in the AM. This is only used in extreme emergencies to
     prevent customer actions from interfering with machine
     operations.

     Min-mode is invoked and deleted via EAI application pokes ``M''
     and ``N,'' respectively.

     The request will display INH when recorded. This inhibit will
     take effect immediately with the request following the next
     major AM initialization.

     The request will clear the text INH when recorded and take
     effect on the next major AM initialization.

     Box 20 - Message Brevity Control

     The box 20 indicator gives inhibit status of message brevity
     control for all messages originating from the application
     processes in the AM only.

     Entering inhibit command 620 generates the message INH:BREVC,AM.
     The request will display INH when recorded. This inhibit will
     take effect immediately with the request.

     Entering the allow command 720 generates ALW:BREVC,AM. The
     request will clear the text INH when recorded.

     This inhibit is cleared by any high-level AM initialization.

     Box 21 - Recent Change Backout

     The box 21 indicator shows whether or not uncommitted (recently
     entered) AM recent changes are loaded or backed out. Backout can
     only occur as a result of an AM high-level initialization.

     The description portion shows when the recent changes are
     actually backed out or loaded. If the backout is in progress, a
     number will appear on the third line of the box showing the
     progress of the backout. From 200 down to 100 is CORC backout;
     200 meaning CORC is still fully backed out and 100 meaning CORC
     is fully rolled forward. From 100 down to 0 is RC backout; 100
     meaning RC is still fully backed out and 0 meaning RC is fully
     rolled forward. Recent changes can be backed out only in
     conjunction with a high-level initialization.

     Recent changes should be backed out if a recent change is
     suspected to be the cause of an AM performance problem.

     When the command 421 is entered, the message SET:BACKOUT,RC,AM
     is generated. The request will display SET when recorded. The
     request state does not necessarily imply that the set is in
     effect.

     When the command 521 is entered, the message CLR:BACKOUT,RC,AM
     is sent. The request will clear the text SET when recorded. The
     request state does not imply that the backout has been cleared.

     Box 22 - Emergency Action Interface/Miscellaneous Checks

     The box 22 indicator shows if Emergency Action
     Interface/Miscellaneous checks are inhibited.  This box includes
     hardware and error interrupts inhibits from the Emergency Action
     Interface page and also error source inhibits.

     When one of the messages INH:ERRINT or INH:ERRSRC is input, it
     will cause the box to backlight.  This box will also backlight
     if error interrupt is inhibited on the Emergency Action
     Interface page.  Input messages ALW:ERRINT or ALW:ERRSRC will
     allow the respective inhibits.

       Note:   The lower portion of this box is lighted only if
               all error interrupt inhibits have been inhibited or
               error source inhibits are inhibited.  If error
               interrupt checks are allowed unit by unit, the
               indicator will not be cleared.

     When the command 922 is entered, the message OP:ERRCHK is sent.
     This generates a listing of the active inhibits.

     Box 23 - Routine Maintenance

     This indicator reflects whether or not a routine maintenance
     function is inhibited.  Should routine maintenance functions be
     inhibited for an extended period of time, various system
     resource availability and consistency may be adversely affected.

     This indicator monitors the AM's Generated Key Collection and
     Compression Routine inhibit status.  If the routine is
     inhibited, the description is backlighted.

     When the 623 command is entered, the message INH:GKCCR,AM is
     sent which requests that automatic executions of the Generated
     Key Collection and Compression Routine be inhibited.

     Entering command 723 generates the command ALW:GKCCR,AM which
     requests that automatic periodic execution of the Generated Key
     Collection and Compression Routine be allowed.

     Box 24 - Hardware Checks

     The box 24 indicator shows whether or not the AM/CM application
     hardware checks have been inhibited.  This indicator can only be
     controlled from the EAI or by TTY input message INH:HDWCHK.
     This inhibit will prevent maskable hardware faults from causing
     recovery.

     Entering the 624 command requests the inhibit of maskable
     hardware faults and generates the message INH:HDWCHK.  The
     request will display INH when recorded.  The request state does
     not necessarily imply that the inhibit is in effect, since the
     status will follow the request within a short period of time.

     If the status is inhibited without being requested, the inhibit
     was automatically applied to the system.

     When the 724 command is entered, the message ALW:HDWCHK is sent.
     The request will clear the text INH when recorded.

     Boxes 25 Through 27 -  Boxes 25 through 27 are not currently
     used.

     Figure .AW G287/ is an example of the 110 page display which shows one
     system inhibit set and two AM inhibits set. Routine Exercises in
     box 17 has been inhibited. Box 21 shows RC BACKOUT is currently
     set and has been partially backed out (80%). However, the top
     line is normal video and there is no SET text after the 21. This
     indicates that the craft does not desire the recent changes to
     be kept out.

     In addition to the following commands, all available display
     commands can be accessed from Display Page 110.
 2

     CMD   RESULT

     421   RC Backout (AM) is set (SET:BACKOUT,RC,AM)
     521   RC Backout (AM) is cleared (CLR:BACKOUT,RC,AM)
     604   Manual RC is inhibited (INH:RC)
     606   RC Logging is inhibited (INH:RCLOG)
     608   CLNK Normalization is inhibited (INH:CLNORM)
     609   CAMA is inhibited (suspended) (INH:CAMAONI)
     616   Routine Audits (AM) are inhibited (INH:AUD=CYCLE,ENV)
     617   Routine Exercises (CM) are inhibited (INH:REX,CM)
     618   Internal Software Checks are inhibited (INH:SFTCHK)
     620   Message Brevity Control (AM) is inhibited (INH:BREVC,AM)
     623   Routine Maintenance (AM) is inhibited; specifically,
           Generated Key Collection and Compression Routine (INH:GKCCR,AM)
     624   Internal Hardware Checks are inhibited (INH:HDWCHK)
     701   Message Class Brevity Control is allowed (ALW:BREVC,MSGCLS=ALL)
     704   Manual RC is allowed (ALW:RC)
     706   RC Logging is allowed (ALW:RCLOG)
     708   CLNK Normalization is allowed (ALW:CLNORM)
     709   CAMA is allowed (no longer suspended) (ALW:CAMAONI)
     716   Routine Audits (AM) are allowed (ALW:AUD=CYCLE,ENV)
     717   Routine Exercises (CM) are allowed (ALW:REX,CM)
     718   Internal Software Checks are allowed (ALW:SFTCHK)
     720   Message Brevity Control (AM) is allowed (ALW:BREVC,AM)
     723   Routine Maintenance (AM) is allowed; specifically,
           Generated Key Collection and Compression Routine (ALW:GKCCR,AM)
     724   Internal Hardware Checks are allowed (ALW:HDWCHK)
     902   Message Class Log/Print Status is output (OP:LPS<MSGCLS=ALL)
     903   MDII Report is output (OP:MDII)
     905   CORC Status is output (OP:STAT,CORC,ACSR)
     910   Trunk Hold list is output (OP:TRUNK)
     916   Routine Audits (AM) are output (OP:AUD,STATUS=ALL,ENV)
     917   Routine Exercises (CM) are output (OP:REXINH,CM)
     922   Listing of active inhibits is output (OP:ERRCHK)


     The purpose of the 115 display page is to provide a summary of
     off-normal status for the hardware units and links which support
     AM to SM(s) communication and provide paths for all circuit
     switched calls.
     The 115 display page has two separate and distinct versions.
     The first version (Figure .AW G288/) is for offices with communication
     module model 2 (CM2) hardware. The second version (Figure .AW G289/)
     is for offices with CM1 hardware.

     The 115 page provides overall status for MSGS 0, MSGS 1, MI/NC 0
     (MI/LI/NC 0 for CM1), MI/NC 1 (MI/LI/NC 1 for CM1), TMS 0, TMS
     1, communication links for the SMs, fan and fan fuse alarms for
     the ONTCs (for the MSGSs and TMSs for CM1), the status of the
     hardware check inhibit request bit, and the status of the
     MI/NC/TMSs (MI/LI/NC/TMSs for CM1) functioning as a group
     (ONTCCOM).

     The ONTCCOM 0 includes MI 0 (and LI 0 in CM1), NC 0, and TMS 0.
     The ONTC 0 includes ONTCCOM 0 and all DLIs on side 0.  The
     ONTCCOM 1 includes MI 1 (and LI 1 in CM1), NC 1, and TMS 1.  The
     ONTC 1 includes ONTCCOM 1 and all DLIs on side 1.

     If an MSGS, MI/NC (MI/LI/NC in CM1), or TMSLNK has an off-normal
     condition (out-of-service not family of equipment, unavailable,
     hardware checks inhibited), the appropriate indicator with the
     page number of the MCC page with the detailed information is
     backlighted. The phrase ``SEE PAGE XXXX IF BACKLIT'' is
     backlighted when any of the boxes are backlighted to point out
     that the numbers in the boxes are the page numbers to request.
     Note: The 1210 boxes are backlighted only for NC reference or
     oscillator problems.

     The CLNKS indicator is a summary of the equipped SM
     communication links status which is detailed on Page 1260.

     The CLNKs are not TMSLNKs.  A CLNK is a communication path
     between the AM and an SM which passes through an MSCU, MMP, TMS,
     TMSLNK, and DLI.  The TMSLNKs connect the TMS to the DLI.

     The backlighted indicator shows the page necessary for acting on
     the problem.  As an example, the box with 1242 indicated is
     backlighted in Figure .AW G288/ because a module message processor
     (MMP) on Display Page 1242 is shown as out of service (OOS).
     The MMP out of service is also reflected on the MSGS 0 Page
     1240, but going to 1240 would not be the final step to see and
     act on the problem so the MSGS 0 box with 1240 indicated is not
     backlighted. If a foundation peripheral controller (FPC) or pump
     peripheral controller (PPC) was out of service also, then the
     MSGS 0 box would backlight as shown in Figure .AW G289/. The purpose
     of this strategy is to get the craft directly to the problem
     with minimum paging.  Therefore, if the 1240 (MSGS 0) box and
     the 1241 (or 1242) were both backlighted, an out of service (not
     family of equipment), an unavailable, an out-of-service power,
     or an unavailable power condition would exist in an MMP and an
     FPC, PPC, or MSCU.

     The TMS 0 and 1 boxes (indicating Page 1220) will never
     backlight. If a TMS is OOS, it would be due to the whole ONTC
     being OOS or UNV; therefore, 1209 is the appropriate page to
     display.

     Figure .AW G288/ shows an example of the CM2 Version with problems in
     MI/NC 1, MSGS 0, TMS 0, CLNKS, and ONTC 1.  Further information
     on these problems would be found on display 1210 - MI/NC 0 & 1,
     1242 - MSGS 0 - COMMUNITIES 2 - 7, 1221 - TMS 0 TMS LINKS 002 -
     063, 1260 - CLNK SUMMARY, and 1209 - ONTC 0 & 1. There is a fan
     alarm on ONTC 0, and the ONTC 1 fan fuse alarm is inhibited.

     Figure .AW G289/ shows an example of the CM1 Version with problems in
     MI/LI/NC 1, MSGS 0, TMS 0, CLNKS, and ONTC 0.  Further
     information on these problems would be found on displays 1210 -
     MI/LI/NC 0 & 1, 1240 - MSGS 0 SUMMARY, 1221 - TMS 0 - TMS LINKS
     002 - 063, 1260 - CLNK SUMMARY, and 1209 - ONTC 0 & 1. There is
     a fan alarm on MSGS 0 and the TMS 0 fan fuse alarm is inhibited.
     The FPC DPLF indicator is signaling that FPC duplex failure is
     in effect.

     There are no menu commands on the 115 display page. Commands for
     removing, restoring, diagnosing, etc., are listed on the related
     pages. There are no menu commands on the displays for fans or
     fan fuses. For fans or fan fuses, see CLR:FANALM in AT&T 235-
     600-700, Input Messages Manual.

     All available display commands can be entered from the 115
     display page.
     The 116 display page provides status for various
     units/activities which do not fall under any other grouping.
     The External Sanity Monitor (ESM) has indicators for alarm,
     inhibit, and power. If an alarm or an inhibit is present, the
     appropriate indicator will backlight. If power is off, the POWER
     indicator will backlight and the word OFF will be displayed.

     The CALL MONITOR indicator shows whether the Call Monitor is
     inhibited or allowed.  Entering the command 601 generates the
     message INH:CALLMON which will inhibit the monitor from making
     test calls and performing call completion analysis.  This also
     clears the monitor's history data.  The command 701 generates
     the message ALW:CALLMON which allows the monitor to start the
     cycle of making test calls and performing call completion
     analysis.  Command 801 generates the message RTR:CALLMON,ALARM
     which retires the alarm indicator in the Call Monitor box.
     Command 901 generates the message OP:CALLMON which generates the
     OP CALLMON PAST 15 MINUTE REPORT on the ROP.

     The indicators FRAME FUSE and FRAME FAN are for the
     miscellaneous frame.  If a fuse or fan alarm is present on the
     miscellaneous frame, the corresponding indicator will backlight.
     The fuse must be replaced to correct the frame fuse alarm.  The
     fan must be restored to operating condition to correct the frame
     fan alarm.  The input command CLR:FANALM,MFFAN can be entered to
     clear the frame fan alarm after the alarm condition is fixed.
     If a system inhibit is present, the word INH will be displayed
     and backlighted to the right of the indicator label.  The fuse
     and fan alarms can only be inhibited by the system.  An inhibit
     means a scan point is chattering.  The input command
     ALW:ALM,MFFAN can be entered to allow the scan point after the
     chattering problem is fixed.

     The indicator GENERIC RETROFIT will backlight and change to
     GENERIC RETROFIT ACTIVE when software release (generic) retrofit
     is in progress.

     The indicator ODD EVOL will backlight and change to ODD EVOL ACT
     when ODD Evolution is in progress. ODD Evolution is initiated by
     the command BKUP:ODD,ODDEVOL and stays in effect until the
     actual software release cutover takes place.

     The indicator OSPS EVOL will backlight and change to OSPS EVOL
     ACT when OSPS Evolution is in progress.  The OSPS Evolution is
     initiated by the command BKUP:ODD,ODDEVOL if the office has an
     OSPS configuration active.  It stays in effect until the actual
     software release cutover takes place.

     The indicator ODD WARNING will backlight when either the amount
     of ODD space being used has exceeded the engineering
     recommendations for the AM or the automatic relation engineering
     reorganization process has failed on one or more relations in
     the AM.  Entering the command 902 generates the input message
     OP:ODDWARN,AM which will generate the OP ODDWARN output message
     on the ROP.

     The RC BACKUP indicator normally says NORMAL on the right part
     of the indicator. If RC Backup fails in the AM, the text NORMAL
     changes to FAILURE and the entire indicator backlights.

     The MISCELLANEOUS ALARMS indicator has two subindicators: ALARM
     and INHIBIT.  These subindicators are backlighted for any alarm
     and/or inhibit conditions present on the MISCELLANEOUS ALARMS
     display.  For additional information, enter command 119.

     The next indicator, MTIB, will backlight if an off-normal
     condition exists on the MTIB display. Enter command 127 for
     further details.

     In the CUTOVER indicator, the word ACTIVE will backlight if an
     off-normal condition exists on the CUTOVER display (cutover
     enabled, for example). Further information can be found on
     display 197 - CUTOVER.

     Any off-normal condition will cause the MISC indicator in the
     SUMMARY STATUS AREA at the top of the screen to backlight.

     Figure .AW G290/ is an example of the 116 display page which shows an
     alarm and an inhibit present on 119 - MISCELLANEOUS ALARMS.
     There is also something off-normal on Page 127 - MTIB STATUS.
     These have caused the MISC status summary indicator at the top
     of the screen to backlight.

     Commands are provided to inhibit and allow the ESM and to clear
     (retire) the exit pilot lamps.  Commands are also provided to
     inhibit and allow the call monitor, output the past 15-minute
     interval history for the call monitor, and retire a call monitor
     alarm.

     Also, all available displays can be accessed from the 116
     display page.

     CMD   RESULT

     600   External Sanity Monitor is inhibited (INH:ALM,ESM)
     601   Call Monitor is inhibited (INH:CALLMON)
     700   External Sanity Monitor is allowed (ALW:ALM,ESM)
     701   Call Monitor is allowed (ALW:CALLMON)
     800   Exit Pilot Lamps are cleared (retired) (CLR:LAMPS)
     801   Call Monitor alarm is retired (RTR:CALLMON,ALARM)
     901   Call Monitor history is output (OP:CALLMON)
     902   ODD WARNING information is output (OP:ODDWARN,AM)

     The purpose of the 117 page display is to provide a summary of
     information associated with the application processor data links
     (APDL).
     The 113 page indicates that maintenance personnel can display
     the 117 page, if desired.

     The following items contain detailed information concerning each
     field in the 117 page display:

       o  LINK:  This field identifies the link by name (for example,
          APDL01).  The 01 attached to the APDL is the link number of
          the link that is added to tuple relation RLCMAPDATA.  The
          link number is between 1 and 6 that corresponds to the
          number assigned to that link via the RC/V view 24.1.

       o  PORT:  This field indicates the data link connected to the
          administrative module-input/output processor (AM-IOP).

       o  MODULE:  This field indicates the data link is connected to
          the AM-IOP.

       o  DEVICE:  This field identifies the PC port and the hardware
          status.  The possible states are as follows: active (ACT),
          out-of-service (OOS), initialization (INIT), or growth
          (GROW).  Also, the UCB of the SDL is indicated.  For
          example, in SDL 42 OOS, 42 is the UCB of the SDL.

       o  PC NAME:  This field identifies the PC on which the port is
          located.  For application processor (AP) data links, there
          is only one port per PC.

       o  SITE_ID:  This field identifies the AP to which the link is
          connected (also known as the AP).  The SITE_ID number
          matches the key field on RC/V view 24.1.

       o  SESSION:  This field indicates the BX.25 session status
          over a given link.  The possible states are as follows:
          connected (CONN), disconnected (DISC), or initialization
          (INIT).

     Figure .AW G291/ shows an example of the 117 page display.

     Any of the available page displays can be accessed from the 117
     page display.

     CMD       RESULT

     121        Peripheral controller status is displayed -- IOP 0 & 1
     122        Peripheral controller status is displayed -- IOP 2 & 3

     The purpose of the 123 display page is to provide status and
     maintenance commands for two DFCs and up to 16 moving head disks
     (MHD).  It also provides status and commands for disk
     independent operation when both essential disks are lost.  In
     5E5 and later software releases, the 123 display page provides
     status of the Auto MHD Configuration feature.

     Prior to the 5E6 software release, the Storage Module Device
     (SMD) was the only disk subsystem associated with the 5ESS(R)
     switch.  Effective with 5E6, the Small Computer Systems
     Interface (SCSI) Bus Interface feature was introduced which can
     either replace or coexist with the SMD.  This means that a 5ESS
     switch office with 5E6 can be only SMD, only SCSI, or both SMD
     and SCSI.

     If there are more than two DFCs in the system, a second DFSA
     page (Page 125) is used.  The format of the 125 page is the same
     as the 123 except the AUTO MHD CONFIGURATION status is not
     shown; it appears only on Page 123.
     The 123 page has three separate and distinct functions.

     The first function of this page is to provide status and
     maintenance commands for DFCs 0 and 1 and associated MHDs (up to
     16).  If the system is equipped with SCSI, this page also
     provides status and maintenance commands for SBUSes (up to 4).

     The second function is to provide status and commands during
     disk independent operation (DIOP).  When both of the MHDs that
     are marked E (essential) go out of service, this page is
     automatically displayed.  This is called full DIOP.  The
     appropriate menu commands to use under these circumstances are
     the 600 series of commands.  When in full DIOP (Figure .AW G293/), a
     620 command will appear which will allow the MHD to be reloaded
     from tape without bringing down call processing during the
     reading of the tape.  When the MHD has been reloaded, a minimum
     of a 52 boot is required.  The other 600 series commands, with
     the exception of the 699 poke, may be used also when not in
     DIOP.  The 699 poke works only in full DIOP.  In 5E7, both the
     602 poke to restore the DFC controller and the 604 poke to
     restore the SBUS controller require UCL when the system is in
     full DIOP.  These pokes (602/604) will not restore associated
     subunits (MHDs) to prevent accidental disk restoral during disk
     maintenance.

     If only one of the essential MHDs goes out of service, the MHDs
     are in simplex operation (Figure .AW G292/), but the page is not
     automatically displayed.

     During full DIOP, the area at the bottom of the page between the
     two horizontal lines will display output messages for the 600
     series menu commands.

     The third function of the 123 page, in 5E5 and later software
     releases, is to provide for the display of the Automatic MHD
     Configuration feature.  The AUTO MHD CONFIGURATION  data
     displayed on 123 page is a summary status of information from
     Pages 178, Auto Spare Disk, and 179, Disk Configuration.

     Possible values of the Automatic MHD Configuration feature are
     as follows:

       a. AUTO MHD CONFIGURATION READY:  The feature is armed and
          ready to run if needed.

       b. SEE PAGE 179, CONFIG MHDs ...:  The listed MHDs have been
          reconfigured; see Page 179 for more data.

       c. AUTO MHD CONFIGURATION OFF:  The feature is turned off.

       d. MHD CONFIG INHIBITED, SEE PAGE 178:  The feature is blocked
          on one or more MHDs or the entire office; see Page 178 for
          more data.

       e. MHD CONFIG IN PROGRESS, SEE PAGE 178:  An MHD configuration
          is in progress; see Page 178 for more data.

     There are two columns of notations on the right side of each of
     the MHD status columns.  The first of the two columns contains
     one of the following two letters:

       o  Y - (Yes):  This means the MHD was diagnosed or restored
          since the last system initialization and appears to be
          usable.

       o  N - (No):  This means the MHD was not diagnosed or restored
          since the last system initialization and does not appear to
          be usable.

     The second column contains the letter E which signifies that the
     associated MHD is essential.

     The upper two display fields, OPTION LEVEL and CURRENT LEVEL,
     inform the user of the optional disk independent operation
     feature level selected for the operating system and the current
     disk independent operation state the operating system is in.

     The OPTION LEVEL displayed will be one of the following:

       o  NODIOP:  Disk independent operation feature is not
          selected.

       o  DIOP:  Conditional disk independent operation is selected.

       o  UCLDIOP:  Unconditional disk independent operation is
          selected.

     The CURRENT LEVEL displayed will be one of the following:

       o  NORMAL:  Normal operating system without disk independent
          operation mode.

       o  SIMPLEX:  Operating system running with at least one
          essential MHD out of service.

       o  DUPLEX:  Operating system is running with all duplex
          essential MHDs active.

       o  CONDITIONAL DIOP:  Operating system is in conditional disk
          independent operation mode with the last remaining duplex
          essential MHD about to be removed from service.

       o  FULL DIOP:  Operating system is running with a duplex
          essential pair of MHDs out of service.

     For each unit displayed, the following information is shown:

       o  Major state of the unit

       o  Minor state of the unit (if available)

       o  Usability of the unit (Y = usable, N = unusable)

       o  Essential status of the unit (E = essential, M = manually
          nonremovable, blank = nonessential)

       o  Microcode status (Firmware of Pumpcode) for the DFC

       o  Overload status of a DFC.

     Figure .AW G292/ shows the simplex version of the disk file system
     access page for an office with SMD only.  In this example, one
     of the essential MHDs (MHD 1) is OOS, so the current level is
     marked as SIMPLEX. The OOS MHD caused the AM PERPH indicator at
     the top of the page to be backlighted.  The automatic MHD
     configuration feature is ready.

     When the simplex mode is entered, the system begins to lock
     essential, nonswappable processes from disk into core (AM
     memory).  Upon completion of the locking process, the system
     will print the message, REPT DIOP SIMPLEX PROCESSING COMPLETED.
     If the system has problems in locking the essential processes
     into core, it will print the message, REPT DIOP SIMPLEX UNSWAP
     FAILURE PID=xx (xx = utility ID of process that failed to lock
     into memory).  This message will reprint every 5 minutes until
     the locking process is completed.

     Figure .AW G293/ shows the FULL DIOP version.

     Figure .AW G294/ shows the simplex version of the disk file system
     access page for an office with SCSI only or with both SMD and
     SCSI.

     The only difference between the SCSI-DFSA and SMD-DFSA versions
     of the 123 page is the addition of ``SBUS 0 SBUS 2'' under DFC
     0, ``SBUS 1 SBUS 3'' under DFC 1 on the SCSI version, and the
     604 command for RST/RMV SBUS.

     Commands are provided to remove, restore, and diagnose the MHDs
     and to take appropriate actions on the MHDs when one or more
     essential MHDs are out of service.

     All available displays can be accessed from the 123 page.
 2
           CMD         RESULT

           2XX         MHD XX is removed from service
                       (RMV:MHD=XX)
           3XX         MHD XX is restored to service
                       (RST:MHD=XX)
           5XX         MHD XX is diagnosed
                       (DGN:MHD=XX)
     600,n [v] [s|d]   MHD n is formatted (initialized)
                       (INIT:MHD=n)
                       v=VFY. Verify option to be used (default=no verify
                       option).
                       s=Track number or range of tracks to be initialized
                       (default=all tracks).
                       d=New. The track number or range of tracks and the
                       ``d'' option can only be used for SMD MHD.
        601,n [s]      MHD n is verified
                       (VFY:MHD=n)
                       where s represents either:
                             t=XX (XX is track number or range of tracks
                             to be verified)
                             (default=all tracks for SMD MHD)
                       or
                             b=XX (XX is block number or range of blocks
                             to be verified)
                             (default=all blocks for SCSI MHD)
                       (For example: 601,0 b=80&&100 will cause the
                       VFY MHD function to be invoked for MHD 0 and will
                       verify blocks 80 through 100 for SCSI MHD.)
        602,n [a]      DFC n controller only is restored
                       a=UCL
                       (RST:DFC=n,CONT)
      603,n [t|fn]     Dump MHD n defect table
                       t=Defect table to be dumped:MFGR,COMB,TEMP,
                       ALL,(default=COMB).
                       fn=Full pathname of a file, in double quotes, that
                       the MFGR defect table is to be written to
                       (DUMP:MHD=n:DEFECT)
       604,n {opt}     RESTORE or REMOVE SBUS
                       {opt} ``RST'' or ``RMV''
                       (RST:SBUS=n,CONT)
                       (RMV:SBUS=n)

                          Note: For SBUS RST, UCL option is required
                          in full DIOP.

         677,n t       Enhanced Information Report (EIR) PRINT
                       n=DFC unit number
                       t=EIR format.  Valid values are ``n''=turn off
                       EIR PRINT, ``l''=long EIR report format,
                       ``s''=short EIR report format
          6XX,h        HELP OPTION
                       Give help for 600 series commands
           688         Clears the buffer
           699         Aborts the menu command that is presently in progress

                          Note:  The 699 poke works only while the
                          system disk is in full DIOP.  It is not effective
                          in normal or simplex modes.

       620,n td a      Loads MHD n from tape drive td using sequence a
                       td=Tape device name
                       a=BOTH,GEN,DBONLY or CONT.

                          Note:  The 620 poke appears only while the
                          system disk is in full DIOP.  It is not effective
                          in normal or simplex modes.


       Note:   The 600 series commands work while the system disk
               is in full DIOP except that pokes 602 (DFC
               controller only restore) and 604 (SBUS controller
               only restore) require UCL.

     The purpose of the 125 display page is to provide status and
     maintenance commands for two DFCs and up to 16 moving head disks
     (MHD).  It also provides status and commands for disk
     independent operation when both essential disks are lost.

     Prior to the 5E6 software release, the Storage Module Device
     (SMD) was the only disk subsystem associated with the 5ESS
     switch.  Effective with 5E6, the SCSI Bus Interface Feature was
     introduced which can either replace or coexist with the SMD.
     This means that an office having the 5ESS switch with 5E6 can be
     only SMD, only SCSI, or both SMD and SCSI.

     This page exists only when there are more than two DFCs in the
     system.

     The format of the 125 page is the same as the 123 except the
     AUTO MHD CONFIGURATION status is not shown; it appears only on
     Page 123.
     The 125 page has two separate and distinct functions.

     The first function of this page is to provide status and
     maintenance commands for DFCs 2 and 3 and associated MHDs (up to
     16).  If the system is equipped with SCSI, this page also
     provides status and maintenance commands for SBUSes (up to 4).

     The second function is to provide status and commands during
     disk independent operation (DIOP).  When in full DIOP, the 125
     page will be accessible.  The 620 poke (reload from tape option)
     will only work on the 123 page.  The other 600 series commands,
     with the exception of the 699 poke, may be used also when not in
     DIOP.  The 699 poke works only in full DIOP.  In 5E7, both the
     602 poke to restore the DFC controller and the 604 poke to
     restore the SBUS controller require UCL when the system is in
     full DIOP.  These pokes (602/604) will not restore associated
     subunits (MHDs) to prevent accidental disk restoral during disk
     maintenance.

     If only one of the essential MHDs goes out of service, the MHDs
     are in simplex operation (Figure .AW G295/), but the page is not
     automatically displayed.

     During full DIOP the area at the bottom of the page between the
     two horizontal lines will display output messages for the 600
     series menu commands.

     There are two columns of notations on the right side of each of
     the MHD status columns.  The first of the two columns contains
     one of the following two letters:

       o  Y (Yes):  This means the MHD was diagnosed or restored
          since the last system initialization and appears to be
          usable.

       o  N (No):  This means the MHD was not diagnosed or restored
          since the last system initialization and does not appear to
          be usable.

     The second column contains the letter E which signifies that the
     associated MHD is essential.

     Figure .AW G295/ shows the simplex version of the disk file system
     access page for an office with SMD only. In this example, one of
     the essential MHDs (MHD 17) has gone out of service, so the
     current level is marked as SIMPLEX. The OOS MHD caused the AM
     PERPH indicator at the top of the page to be backlighted.

     When the simplex mode is entered, the system begins to lock
     essential, nonswappable processes from disk into core (AM
     memory).  Upon completion of the locking process, the system
     will print the message, REPT DIOP SIMPLEX PROCESSING COMPLETED.
     If the system has problems in locking the essential processes
     into core, it will print the message, REPT DIOP SIMPLEX UNSWAP
     FAILURE PID=xx (xx = utility ID of process that failed to lock
     into memory).  This message will reprint every 5 minutes until
     the locking process is completed.

     Figure .AW G296/ shows the simplex version of the disk file system
     access page for an office with SCSI only or with both SMD and
     SCSI.

     The only difference between the SCSI-DFSA and SMD-DFSA versions
     of the 125 page is the addition of ``SBUS 0 SBUS 2'' under DFC
     2, ``SBUS 1 SBUS 3'' under DFC 3 on the SCSI version, and the
     604 command to RST/RMV SBUS.

     Commands are provided to remove, restore, and diagnose the MHDs
     and to take appropriate actions on the MHDs when one or more
     essential MHDs are out of service.

     All available displays can be accessed from the 125 page.
 2
           CMD         RESULT

           2XX         MHD XX is removed from service
                       (RMV:MHD=XX)
           3XX         MHD XX is restored to service
                       (RST:MHD=XX)
           5XX         MHD XX is diagnosed
                       (DGN:MHD=XX)
     600,n [v] [s|d]   MHD n is formatted (initialized)
                       (INIT:MHD=n)
                       v=VFY. Verify option to be used (default=no verify
                       option).
                       s=Track number or range of tracks to be initialized
                       (default=all tracks).
                       d=New. The track number or range of tracks and the
                       ``d'' option can only be used for SMD MHD.
        601,n [s]      MHD n is verified
                       (VFY:MHD=n)
                       where s represents either:
                             t=XX (XX is track number or range of tracks
                             to be verified)
                             (default=all tracks for SMD MHD) or
                             b=XX (XX is block number or range of blocks
                             to be verified)
                             (default=all blocks for SCSI MHD)
                       (For example: 601,0 b=80&&100 will cause the
                       VFY MHD function to be invoked for MHD 0 and will
                       verify blocks 80 through 100 for SCSI MHD.)
        602,n [a]      DFC n controller only is restored
                       a=UCL
                       (RST:DFC=n,CONT)
      603,n [t|fn]     Dump MHD n defect table
                       t=Defect table to be dumped:MFGR,COMB,TEMP,
                       ALL,(default=COMB).
                       fn=Full pathname of a file, in double quotes, that the
                       MFGR defect table is to be written to
                       (DUMP:MHD=n:DEFECT)
       604,n {opt}     RESTORE or REMOVE SBUS
                       {opt} ``RST'' or ``RMV''
                       (RST:SBUS=n,CONT)
                       (RMV:SBUS=n)

                          Note: For SBUS RST, UCL option is required
                          in full DIOP.

         677,n t       Enhanced Information Report (EIR) PRINT
                       n=DFC unit number
                       t=EIR format.  Valid values are ``n''=turn off
                       EIR PRINT, ``l''=long EIR report format,
                       ``s''=short EIR report format
          6XX,h        HELP OPTION
                       Give help for 600 series commands
           688         Clears the buffer
           699         Aborts the menu command that is presently in progress

                          Note:  The 699 poke works only while the
                          system disk is in full DIOP.  It is not effective
                          in normal or simplex modes.

       620,n td a      Loads MHD n from tape drive td using sequence a
                       td=Tape device name
                       a=BOTH,GEN,DBONLY or CONT.

                          Note:  The 620 poke appears only while the
                          system disk is in full DIOP.  It is not effective
                          in normal or simplex modes.


       Note:   The 600 series commands work while the system disk
               is in full DIOP except that pokes 602 (DFC
               controller only restore) and 604 (SBUS controller
               only restore) require UCL.

     The 130 display page provides status of the manual and automatic
     NM system controls and status of NM circuit conditions. Also, it
     provides a command to get a listing of any NM controls that are
     YES.
     When there is an overload in the system there are manual or
     automatic controls that can be put on the system by Network
     Management. The 130 page shows the status of these controls,
     either YES or NO.

     Any controls on this page that are YES will cause an indicator
     that refers to this page to appear and be backlighted on Page
     109 - OVERLOAD. In the STATUS SUMMARY AREA at the top of the
     screen, the OVERLOAD status summary indicator will be
     backlighted. This page also has a reference back to Page 109
     that is displayed all the time.

     Figure .AW G297/ shows there is a manual control on the CALL GAP and
     transmit (XMT) of dynamic overload control (DOC) is allowed
     (ALW).

     The command on this page is provided to print a listing of any
     NM controls that are YES. Also, any available paging commands
     can be entered from this display.

     CMD   RESULT

     900   Any YES NM controls are output (OP:NMPGE)

     The purpose of the 141 through 144 display pages is to provide a
     more detailed summary status of groups of 48 SMs on one display.
     Displays 141, 142, 143, and 144 are very similar. Each one can
     display summary status of up to 48 SMs. Page 141 displays status
     for SMs 1 through 48, Page 142 displays summary status for SMs
     49 through 96, Page 143 displays status for SMs 97 through 144,
     and Page 144 displays summary status for SMs 145 through 192.

     Each equipped SM has a unique indicator on these displays. Each
     indicator has the following three distinct sections:

       o  SM NUMBER: There may be gaps in SM numbering for a
          particular office.  To provide flexibility in office
          numbering schemes, the SM numbers are not necessarily
          assigned sequentially. If an SM is not equipped, it is not
          shown. An example of this is shown in the 141 page example
          (Figure .AW G298/) by the blank indicators between SM 12 and SM
          20, SM 20 and SM 24, etc.

       o  SM TYPE: There is a 3-character acronym to show how an SM
          is being used. For example, an LSM is a local switching
          module.

       o  SM STATUS PHRASE: This is a 10-character, maximum, phrase
          which describes the most significant off-normal condition
          in the SM.  During initialization, the status phrase will
          give the current initialization progress type.  Table .AW TAK/
          lists status phrases in order of priority and gives the
          color and an explanation for each phrase. New phrases for
          5E7 are E911 CRIT and ODD WARN.  For detailed information
          on SM progress markers, see AT&T 235-105-250, System
          Recovery.

     If more than one off-normal condition exists in an SM, a ``+''
     will appear to the right of the status phrase (SMs 1, 5, and 48
     in Figure .AW G298/).  A complete list of active off-normal conditions
     can be output via menu command 900.

     In addition to this page, the status phrase is shown on all
     per-SM pages.

     When a new alarm condition on an SM occurs, the SM indicator
     will begin flashing. The ALM RLS key will not stop the flashing.
     The color of the flashing will reflect the new alarm only if the
     newly recorded condition is of higher or equal priority to the
     previous condition. To stop the flashing, the craft should
     display the 1010 page for that SM. There is also a command to
     retire the flashing for the range of SMs associated with the
     page being displayed - 999. This is mainly provided for
     situations such as during installation when SMs are being grown
     and many SMs are displaying recurrent error conditions.

     The backlighted note about the DLIs appears whenever an ONTC is
     out of service or unavailable. The DLIs are under the
     maintenance control of the ONTCs, thus all DLIs on a side are
     affected when the ONTC of that side is off-normal.

     For further details on any SM recovery-related activity or SM
     inhibits, the craft would enter 1800,X to display the SM X
     INHIBIT AND RECOVERY CONTROL page. This is the SMs control page
     for emergency action.

     For details on circuits out of service or hardware in a
     particular SM, the craft would enter 1010,X to display the SM X
     STATUS page. This page can be accessed during the initialization
     of SM X or if SM X is isolated, but the only status that will
     fill in are the SM STAT and RELATED PAGES boxes.

     For details on ONTC circuits out of service, the craft would
     enter 115 to display the COMMUNICATION MODULE SUMMARY page.

     In the example of the 141 page shown in Figure .AW G298/, SM 1, which
     is an LSM, has several off-normal conditions. The ``+''
     indicates that there is more than one off-normal condition.  For
     the most critical condition, inhibits are set. Both SM 3 and 10
     have circuits out of service.  The SM 5, an RSM, has a hash
     error plus other off-normal conditions.  The SM 06, another LSM,
     is isolated. This indicator would be flashing in the display,
     which cannot be shown here.  The SM 48, another RSM, has a
     building power alarm plus other off-normal conditions.  There is
     an off-normal condition in ONTC 1 causing all the DLIs on Side 1
     to be off-normal.

     All available displays can be accessed from the 141 through 144
     display pages.

       CMD     RESULT

       900     The off-normal report is output for the SMs associated
               with the page
               (OP:SYSSTAT,SM=a&&b) [,LSM] [,HSM] [,RSM] [,UCL]
               where a&&b is the range of SMs associated with the page
               being displayed
       999     SM flashing is retired for the range of SMs associated with
               the page
     1010,X    SM X STATUS page is displayed
      1271     SM 1 - 48 REX SUMMARY page is displayed
     1600,SZ   SITE Z STATUS page is displayed
     1800,X    SM X INHIBIT AND RECOVERY CONTROL page is displayed

     The SM Page Index page provides an index to the SM and remote
     switching module/remote integrated services line unit
     (RSM/RISLU) pages.
     The 1000 page is an index to the primary SM/RSM/RISLU pages that
     directly have status reflected on the 1010 - SM X STATUS page.
     No status is displayed on the 1000 page.

     The page is divided into two parts. The first part displays all
     the pages that are valid for local switching modules (LSM), host
     switching modules (HSM), and RSMs/RISLUs. The second part
     displays the pages that are only valid for RSMs/RISLUs and
     remote sites.

     Some pages shown on the 1000 page reference additional pages
     that provide more detailed information.  These additional pages
     may not appear on the 1000 page.

     Most SM pages are specified using an SM number.  Some pages,
     however, are referenced by the site number of a remote site.
     For these pages (such as the 1600,SZ page), the ``S'' shown on
     the 1000 page is actually entered as part of the menu command.
     For example, entering ``1600,S3'' will display the status of
     RSMs/HSMs at Site 3.

     For all pages, once an SM page has been displayed for a
     particular SM, any other page for that SM may be requested
     without respecifying the SM number.

     The index shown in Figure .AW G299/ is a listing of the primary SM and
     SITE maintenance displays for the 5E7 software release.

     All available paging commands can be entered from this display.

 4
     LSM and HSM Pages

      CMD                             RESULT

     1010,X   SM X - STATUS page is displayed
     102Y,X   SM Y - LU X CONCENTRATOR page is displayed, if equipped
     103Y,X   SM X - LU Y SG 0 page is displayed, if equipped
     104Y,X   SM X - LU Y SG 1 page is displayed, if equipped
     105Y,X   SM X - TU Y SG 0 page is displayed, if equipped
     106Y,X   SM X - TU Y SG 1 page is displayed, if equipped
     107Y,X   SM X - DCTU Y page is displayed, if equipped
     108Y,X   SM X - LDSU Y SG 0 AND 1 page is displayed, if equipped
     109Y,X   SM X - RAF Y page is displayed
     110Y,X   SM X - GDSU Y page is displayed, if equipped
     1110,X   SM X - ISTF page is displayed
     112Y,X   SM X - DLTU Y page is displayed, if equipped
     113Y,X   SM X - MSU Y SG 0 page is displayed, if equipped
     114Y,X   SM X - MSU Y SG 1 page is displayed, if equipped
     115Y,X   SM X - DCLU Y page is displayed, if equipped
     1186,X   SM X - PSU NETWORK page is displayed
     1190,X   SM X - MCTSI page is displayed
     1200,X   SM X - DLI/TMSLNK page is displayed
     1280,X   SM X - REX STATUS page is displayed
     1460,X   SM X - DATA LINK DSLS page is displayed
     170Y,X   SM X - ISLU Y NETWORK page is displayed
     1800,X   SM X - INHIBIT AND RECOVERY CONTROL page is displayed
     1900,X   SM X - CLNKS page is displayed

 4
     RSM/RISLU PAGES

       CMD                                 RESULT

     1160,X    SM X - MISC UNITS page is displayed, if equipped
     1170,X    SM X - RCLK page is displayed, if equipped
     1190,X    SM X - MCTSI/RLI page is displayed
     1400,X    SM X - RSM BLDG/PWR ALARMS page is displayed, if equipped
     1420,SZ   RISLU BLDG/PWR page is displayed
     145Y,X    RISLU DLTU Y page is displayed
     1600,X    SM X - SITE STATUS page is displayed via SM number, if
               equipped
     1600,SZ   RSM/RISLU SITE STATUS page is displayed
      1610     RSM SITE INDEX page is displayed
      1615     ORM SITE INDEX page is displayed
     1620,SZ   RISLU SITE STATUS page is displayed
      1630     RISLU SITE INDEX page is displayed
     170Y,X    RISLU Y NETWORK page is displayed

       Note:   The term basic rate interface (BRI) means the same
               thing as digital subscriber line (DSL).  This
               document uses DSL, because the 1460 page display
               does not identify BRI.

     The 1460 page display provides summary status of the Operator
     Services Position System (OSPS) data links on a per-SM basis.
     The 1460 page display is not normally accessed when DSLs are IN
     SERVICE.  Usually the 1460 page is accessed because of the
     following:

       o  DSL MAJOR or DSL MINOR alarm is indicated in the SM X
          STATUS indicator box on the 1010-SM X LSM STATUS page
          display.

       o  SEE 1460 is present in the RELATED PAGES box on the 1010-SM
          X LSM STATUS page.

     The 1460 page display provides the following information:

       o  Which data link types are equipped in an SM.

            Note:   If no ports are equipped for a specific data
                    link in the SM, then no data link block
                    appears on the 1460 page display.

       o  Which data link types have ports OOS and the relative
          seriousness of the fault.  Each data link type has an
          associated indicator block.  If a block is backlighted red,
          a minor alarm is indicated; also, the term DSL_MINOR is
          displayed in the SM XXX STATUS indicator block.  If a block
          is flashing from red to white, a major alarm is indicated;
          also, the term DSL_MAJOR is displayed in the SM XXX STATUS
          indicator block.

       o  Which page display gives more details (for example,
          equipment numbers or states) concerning each data link type
          equipped in an SM.  On the 1460 page display (Figure .AW G300/),
          one of the data links represented is DAS/C with the
          associated page to see for more details (for example, SEE
          147000).  Where the first two zeros = the data link type
          (service class) and the last zero indicates the screen
          number of the specific service class.

            Note:   Figure .AW G261/ is an example of the XDB data link
                    page display (147072 - SM 017 LSM - XDB   DATA
                    LINKS).  This page identifies the global port
                    names, external names, and port status for the
                    data links of a specific type equipped on the
                    SM.

     There are two types of data links (service classes) - simplex
     and duplex.  The following are simplex data links:

       Note:   The XDB data link is the only link that can be
               equipped with more than 16 ports.

       o  HOBICV

       o  HOBIS

       o  HOBICR

       o  AQ

       o  XDB

       o  OAP.

     The following are duplex data links:

       o  DAS/C

       o  RAS

       o  RTRS

       o  MISLNK.

     The external information system (EIS) data link introduced in
     5E6 is an N+K data link group, where N+K is defined in the
     alarms section.

     Major and Minor Alarms

     For simplex data links, if more than 50 percent of the ports
     associated to a specific data link (per-SM) are OOS (out of
     service), a major alarm occurs.

     For simplex data links, if one but no more than 50 percent of
     the ports associated to the data link are OOS, a minor alarm
     occurs.

       Note:   If exactly 50 percent of the ports associated to a
               specific data link are OOS, a minor alarm occurs.

     For the duplex DAS/C and RTRS data links, the DAS and RTRS data
     links can be equipped with a maximum of two ports each.  If only
     one port is assigned to DAS/C or RTRS and the port is OOS, a
     major alarm occurs.  If two ports are assigned to DAS/C or RTRS
     and one port is OOS, a minor alarm occurs; and if both ports are
     OOS, a major alarm occurs.

     For the duplex RAS data link, a maximum of eight RISLUs can be
     equipped with RAS (that is, on a per-SM basis).  Each RISLU site
     can be assigned up to a maximum of two RAS data links,
     therefore, providing a maximum of 16 data links per SM.  A minor
     alarm occurs when at least one RAS data link is OOS, but all of
     the RISLU sites have at least one RAS link in service.  A major
     alarm occurs when at least one site has all RAS links OOS.  Some
     RISLU sites may only be equipped with one RAS link; when or if
     this link is OOS, a major alarm occurs.

     For the OAP data links, if one of the data links is OOS or
     transitions from IS to IS/INIT, a major alarm occurs.  Minor
     alarms do not apply to the OAP.

     EIS Alarm Strategy

     The following terminology is used to define EIS data link alarm
     strategy for an SM:

     The set of EIS data links equipped on a specific SM and
     connected to a specific EIS is referred to as an ``EIS Call
     Processing Data link (CPDL) group.''  Each EIS CPDL group
     consists of (N+K) data links, where N and K are specified
     independently for each EIS CPDL group as follows:

       1. N, indicating the minimum number of CPDLs that are needed
          to support the message traffic during the busy hour for the
          EIS CPDL group.

       2. K, the number of CPDLs providing surplus traffic capacity
          for the EIS CPDL group.

     The EIS data link summary status for an SM is defined as
     follows:

       o  DSL_NORMAL:  All EIS data links on the SM are in service.

       o  DSL_MINOR:  At least one EIS data link equipped on the SM
          is out of service, but each EIS CPDL group has at least N
          EIS data links in service.

       o  DSL_MAJOR:  At least one EIS CPDL group has fewer than N
          EIS data links in service.

     Figure .AW G300/ shows an example of the 1460 page display.

     Any available paging commands can be entered from this display.
     The 171Y,X page display provides status and menu selection for
     the maintenance actions of the ISLUMAN, ISLURG, and ISLUHLSC.
     The last digit of the page number indicates the ISLU number (for
     example, 1712).  The ISLU numbers range from 1710 through 1717.

     This page (one per ISLU) displays the status of each ISLUHLSC,
     ISLUMAN, and ISLURG in both SGs 0 and 1.  The possible states of
     these indicators are ``ACT,'' ``CAMP,'' ``OOS,'' ``OOSFE,''
     ``DGR,'' ``GROW,'' and ``UNEQ.''  When any of the circuits in an
     ISLU SG are in an off-normal state, the associated SG summary
     status indicator for that SG is backlighted.

     The 171Y,X page can be accessed from the 170Y - SM ISLU NETWORK
     page display.

     Figure .AW G301/ shows an example of the 171Y,X page display.

     Commands are provided to remove, restore, and diagnose the
     ISLUMAN, ISLUHLSC, and ISLURG of the SG.  Also, the ISLU Line
     Group page display can be requested.  Any available paging
     commands can be entered from this page.

      CMD     RESULT

      20XY    Removes SG X ISLUMAN Y (RMV:ISLUMAN=a-b-x-y)
      21XY    Removes SG X ISLUHLSC Y (RMV:ISLUHLSC=a-b-x-y)
      22X     Removes ISLURG SG X (RMV:ISLURG=a-b-x)
      30XY    Restores SG X ISLUMAN Y (RST:ISLUMAN=a-b-x-y)
      31XY    Restores SG X ISLUHLSC Y (RST:ISLUHLSC=a-b-x-y)
      32X     Restores ISLURG SG X (RST:ISLURG=a-b-x)
      50XY    Diagnoses SG X ISLUMAN Y (DGN:ISLUMAN=a-b-x-y,RAW,TLP)
      51XY    Diagnoses SG X ISLUHLSC Y (DGN:ISLUHLSC=a-b-x-y,RAW,TLP)
      52X     Diagnoses ISLURG SG X (DGN:ISLURG=a-b-x)
     170YZZ   Displays ISLU Y LG ZZ

     The 1800,X page provides inhibit and recovery status and control
     information for SM X.  It functions like an emergency action
     interface for the SM.
     When an inhibit is requested, the top third of the associated
     indicator will be backlighted to the INHIBIT state and the text
     INH will appear in the corresponding box. When the inhibit is
     actually activated, the rest of the associated indicator will be
     backlighted to the INHIBIT state. On Page 114 - EQUIPPED SM
     STATUS SUMMARY, the indicator for that SM will be backlighted;
     and on the appropriate 141, 142, 143, or 144 page, the indicator
     for that SM will be backlighted and the phrase INHIBITS will be
     written, unless a more critical condition exists. In the SUMMARY
     STATUS AREA, the SM critical indicator will be backlighted.

     Some of the boxes on the 1800,X page have numbers at the bottom
     of the box. These numbers show what commands are available from
     the display. For example, at the bottom of Box 02 the numbers
     ``6 7 9'' appear. The ``6'' means this item can be inhibited by
     entering 602, the ``7'' means it can be allowed by entering 702,
     and the ``9'' means output is available with 902.  On color MCC
     terminals, there is also color mapping from the commands shown
     on the left of the display to the numbers in the boxes.

     In addition to the inhibit status indicators, there are
     indicators for the status of the module controller time slot
     interchangers (MCTSI)  0 and 1. When the MCTSIs are functioning
     normally, the active MCTSI is marked active (ACT). If an MCTSI
     is active forced, it is shown as ACTF and the other MCTSI is
     marked unavailable (UNAV). The conditions standby and out of
     service also apply to this display. During an initialization,
     the status of the inactive MCTSI cannot be precisely determined
     and the display will be blanked.

     There is also an indicator for the state of the mate memory.
     The possible states for the mate memory indicator are as
     follows:

       o  STANDBY:  Mate memory has been updated

       o  UPDATING:  Mate memory update is in progress

       o  OOD:  Mate memory is out of date

       o  PUMPED:  Mate memory has been off-line pumped.

     During an initialization, the status of the mate memory cannot
     be precisely determined and the display will be blanked.  The
     lower area of the SM STAT indicator is for listing special
     abnormal conditions in the SM. The possible conditions shown in
     this area are as follows: GEN DIFF, ISOLATED, COMMLOST, SPEC
     GROW, STNDALONE, INIT PEND, and HASH ERR.
     This section describes the individual indicators and their
     behavior.

     Box 00 Routine Audits

     This indicator shows if the automatic execution of the SM audit
     cycle is inhibited.

     Entering the 600 command generates the command
     INH:AUD=CYCLE,SM=X and causes the top line of the indicator to
     be backlighted and the text INH to be written. This request is
     phase-protected. Single audits can also be inhibited via input
     messages, but they are not phase-protected.

     When the request is recorded, the description area of the box is
     backlighted. This area is backlighted if one or more of the SM
     audits are inhibited.

     Entering the command 700 generates the command
     ALW:AUD=CYCLE,SM=X and causes the indicator to return to normal
     video.

     The command 900 can be entered to get a ROP listing of routine
     audit status for the SM. This command generates the message
     OP:STATUS=ALL,AUD,SM=X.

     Box 01 Auto Pump

     When the 601 command is entered, it generates the command
     INH:PUMP,SM=X. This inhibits the automatic pump of the SM on a
     major initialization (except UNIX(R) RTR system level D4). This
     inhibit is phase-protected.

     The 701 command generates ALW:PUMP,SM=X. This command must be
     entered to cancel the inhibit.

     Box 02 Routine Exercises

     This indicator shows if any or all of the routine exercises
     (other than unit exercises) in the SM are inhibited.

     Entering the command 602 generates the message INH:REX,SM=X.
     Entering the command 702 generates the message ALW:REX,SM=X.  To
     print a status listing of routine exercises at the ROP, enter
     the 902 command (OP:REXINH,SM=X).

     Box 03 Manually Isolate

     When the 403 command is entered, it generates the message
     SET:ISOL,SM=X. This configures CLNK hardware to remove any level
     2 protocol or active links from service. The removal is
     unconditional, and the SM will remain isolated until the 503
     command is entered which generates the message CLR:ISOL,SM=X.

     Box 04 Software Checks

     This indicator reflects whether or not the AM application
     software checks are inhibited. If any software checks have been
     inhibited, the description section is backlighted.

     The command 604 generates the message INH:SFTCHK,SM=X and 704
     generates ALW:SFTCHK,SM=X.

     Box 05 Sanity Timer

     This box provides commands to inhibit and allow the sanity
     timer.

     The command 605 generates the message ORD:CPI=X,CMD=INH and 705
     generates ORD:CPI=X,CMD=ALW.

     Box 06 Customer-Originated Recent Change (CORC) Logging

     The command 606 generates the message INH:CORCLOG,SM=X which
     causes the CORC logging to be inhibited.

     Inhibiting customer-originated recent change logging should only
     be used when recent change logging is suspected to be causing a
     problem in the system.

     The command 706 generates the message ALW:CORCLOG,SM=X.

     Box 07 Recent Change Backout

     This indicator shows the status of recent change (RC) backout.
     If set, RCs will not be reentered following a high-level
     initialization.

     The description portion shows when the recent changes are
     actually backed out or loaded. If the backout is in progress, a
     number will appear on the third line of the box showing the
     progress of the backout. From 200 down to 100 is CORC backout;
     200 meaning CORC is still fully backed out and 100 meaning CORC
     is fully rolled forward. From 100 down to 0 is RC backout; 100
     meaning RC is still fully backed out and 0 meaning RC is fully
     rolled forward. Recent changes can be backed out only in
     conjunction with a high-level initialization.

     The command 407 generates the message SET:BACKOUT,RC,SM=X and
     507 generates CLR:BACKOUT,RC,SM=X.

     Box 08 Hardware Checks

     The command 608 (INH:HDWCHK,SM=X) causes all SM hardware checks
     to be inhibited. Note: The lower portion of this box is lighted
     only if all hardware checks have been inhibited.

     If hardware checks are allowed circuit by circuit, the indicator
     will not be cleared.

     The command 708 (ALW:HDWCHK,SM=X) allows all SM hardware checks.
     This will clear the backlighting of the box.

     Box 09 SM Brevity Controls

     Certain messages are normally suppressed from printing at the
     ROP. By inhibiting the controls, all SM output messages would be
     sent to the AM regardless of past message counts. Using this
     command can increase link traffic to the AM, and thus, can be
     service affecting.

     Inhibiting the brevity controls is achieved by entering command
     609 (INH:BREVC,SM=X). The controls can be returned to normal by
     entering the command 709 (ALW:BREVC,SM=X).

     Box 10 UPD Backout

     This indicator shows whether or not recently applied SM program
     updates are currently loaded or backed out.

     The description portion shows when the program updates are
     actually backed out or loaded. Program updates can be backed out
     or loaded only in conjunction with a high-level initialization.

     There are no menu commands for this box.

     Box 11 Min Mode (Full Init)

     This inhibit causes the SM to enter minimum mode and ignore all
     call processing. This inhibit should only be used in extreme
     emergencies, when all other normal recovery procedures have
     failed.

     When the 411 command is entered, the message SET:MINMODE,SM=X,FI
     is sent. This initiates a high-level init and inhibits software
     checks, hardware checks, routine exercises, and routine audits.
     In addition, output message brevity control is allowed.

     The only way to exit min mode is to enter the clear command or
     message. The 511 command generates the message
     CLR:MINMODE,SM=X,FI and causes a high-level init.

     Box 12 Peripheral Fault Recovery Message Verbose

     The command 412 (SET:PERPH,SM=X, VERBOSE) causes peripheral
     fault recovery (PFR) to send to the AM peripheral error messages
     that indicate that no recovery action has occurred in addition
     to messages that indicate that a peripheral error has caused
     recovery actions.

     The command 512 (CLR:PERPH,SM=X, VERBOSE) causes PFR to suppress
     the output of error reports. In the normal state, only output
     messages which indicate that a peripheral error has caused
     recovery actions on a circuit will be output.

     The messages will be logged or printed, depending on the state
     of the message class for each peripheral unit type.

     Box 13 Alarmed Message Discard

     This indicator shows if any output messages for this SM are
     being discarded.  Output messages of CRITICAL, MAJOR, MINOR, or
     MANUAL can be discarded by the input message CHG:MSGCNTL.  When
     this input message is entered, the box will be backlighted.

     Box 14 - Routine Maintenance

     This indicator reflects whether or not a routine maintenance
     function is inhibited.  Should routine maintenance functions be
     inhibited for an extended period of time, various system
     resource availability and consistency may be adversely affected.

     This box monitors the SM's Generated Key Collection and
     Compression Routine inhibit status.  If the routine is
     inhibited, the description section is backlighted.

     When the 614 command is entered, the message INH:GKCCR,SM=X is
     sent which requests that automatic executions of the Generated
     Key Collection and Compression Routine be inhibited.

     Entering command 714 generates the command ALW:GKCCR,SM=X which
     requests that automatic periodic execution of the Generated Key
     Collection and Compression Routine be allowed.

     Box 15 - Box 15 is currently not used.

     Figure .AW G302/ is an example of the 1800,X page which shows the SM 1
     sanity timer inhibited; MCTSI 0 is active and MCTSI 1 is in
     standby. The mate memory is out of date and 50 percent of the
     recent change has been backed out.

     Any available paging command can be entered from the 1800,X
     display page.

     Input messages for commands shown in boxes on the display are
     also described previously under the subheading, Indicators.

 2
     CMD   RESULT

     403   Manual Isolation of SM is set (SET:ISOL,SM=X)
     407   RC Backout is set (SET:BACKOUT,RC,SM=X)
     411   Min Mode (FI) is set (SET:MINMODE,SM=X,FI)
     412   Peripheral fault recovery message verbose is set
           (SET:PERPH,SM=X,VERBOSE)
     420   MCTSI 0 is forced active (SET:MCTSI=X-0,FRC)
     421   MCTSI 1 is forced active (SET:MCTSI=X-1,FRC)
     422   Force of MCTSI is cleared (CLR:MCTSI=X,FRC)
     503   Manual Isolation of SM is cleared (CLR:ISOL,SM=X)
     507   RC Backout is cleared (CLR:BACKOUT,RC,SM=X)
     511   Min Mode (FI) is cleared (CLR:MINMODE,SM=X,FI)
     512   Peripheral fault recovery message verbose is cleared
           (CLR:PERPH,SM=X,VERBOSE)
     600   Routine Audits are inhibited (INH:AUD=CYCLE,SM=X)
     601   Auto Pump is inhibited  (INH:PUMP,SM=X)
     602   Routine Exercises are inhibited (INH:REX,SM=X)
     604   Software Checks are inhibited (INH:SFTCHK,SM=X)
     605   Sanity Timer is inhibited (ORD:CPI=X,CMD=INH)
     606   CORC Logging is inhibited (INH:CORCLOG,SM=X)
     608   All Hardware Checks are inhibited (INH:HDWCHK,SM=X)
     609   Brevity Control for the SM is inhibited (INH:BREVC,SM=X)
     614   Routine Maintenance function is inhibited; specifically,
           Generated Key Collection and Compression Routine (INH:GKCCR,SM=X)
     700   Routine Audits are allowed (ALW:AUD=CYCLE,SM=X)
     701   Auto Pump is allowed (ALW:PUMP,SM=X)
     702   Routine Exercises are allowed (ALW:REX,SM=X)
     704   Software Checks are allowed (ALW:SFTCHK,SM=X)
     705   Sanity Timer is allowed (ORD:CPI=X,CMD=ALW)
     706   CORC Logging is allowed (ALW:CORCLOG,SM=X,)
     708   All Hardware Checks are allowed (ALW:HDWCHK,SM=X)
     709   Brevity Control for the SM is allowed (ALW:BREVC,SM=X)
     714   Routine Maintenance function is allowed; specifically,
           Generated Key Collection and Compression Routine (ALW:GKCCR,SM=X)
     900   Routine Audits are output (OP:STATUS=ALL,AUD,SM=X
     902   Routine Exercises are output (OP:REXINH,SM=X)
     920   Selective initialization is requested (INIT:SM=X,SI)
     921   Selective initialization with pump is requested
           (INIT:SM=X,SI,PUMP)
     922   Full Initialization is requested (INIT:SM=X,FI)
     923   Full Initialization with pump is requested (INIT:SM=X,FI,PUMP)
     924   Forces the reset counter to level 12 or greater (guaranteeing
           a high level init).  This poke does not require software sanity
           in the SM.  Poke 924 uses central processor intervention (CPI)
           to force the SM to reset, and the ROM reset handler forces the
           reset count to level 12 or greater. The remainder of the init
           occurs normally (ORD:CPI=X,CMD=RESET).

              Note:  If the SM fails to respond to the FI PUMP and the
              SM appears to have lost sanity, use MP RESET (924 poke).  Also,
              if the SM is attempting to pump and is failing, then MP RESET
              may not help.

     The 1850 page provides status displays for both the primary and
     mate CMPs of the pair.  Also provided are menu commands to
     inhibit or allow hardware and software checks, routine audits,
     automatic pump, brevity control, and set and clear for recent
     change backout.  Requests for high-level initialization can be
     poked from the 1850 page.
     On the 1850 page display, each processor is identified by its
     CMP pair number and by its physical representation which
     includes the message switch side.  There will be only one
     primary/mate CMP pair (0) for 5E6 and later.

     During CMP initialization, the initialization status phrase
     progress marks will be displayed in the PRIM STAT portion of the
     screen along with the progress counter which shows the progress
     within a particular phase of the initialization.  The set of
     progress marks used will be different from the set used for the
     SMs pump and initialization sequences on MCC Page 1800,X.

     Table .AW TAL/ shows the CMP Off-Normal Status Phrases along with the
     priority, color, and an explanation of each.

     After initialization has completed, the current (highest) level
     CMP status will be displayed (just as with the SMs on the 1800,X
     page).  A ``+'' sign at the end of the status phrase indicates
     that more than one off-normal status exists.  The OP:SYSTAT
     input message or 800 poke command can be used to obtain
     additional off-normal status information.  Also, the current
     (highest) status of the MATE CMP will be displayed.  Additional
     status phrases are displayed in the other PRIM STAT and MATE
     STAT boxes along with the peripheral control data (PCD) status.

     Some of the boxes on the 1850 page have numbers at the bottom.
     These numbers show what commands are available from the display.
     For example, at the bottom of Box 00 the numbers ``6 7 9''
     appear. The ``6'' means this item can be inhibited by entering
     600, the ``7'' means it can be allowed by entering 700, and the
     ``9'' means output is available with 900.  On color MCC
     terminals, there is also color mapping from the commands shown
     on the left of the display to the numbers in the boxes.
     This section describes the individual indicators and their
     behavior.

     Box 00 - Routine Audits

     This indicator shows if the automatic execution of the CMP audit
     cycle is inhibited.

     Entering the 600 command generates the command INH:AUD[=a],CMP=b
     and causes the top line of the indicator to be backlighted and
     the text INH to be written. This request is phase-protected.
     Single audits can also be inhibited via input messages, but they
     are not phase-protected.

     When the request is recorded, the description area of the box is
     backlighted. This area is backlighted if one or more of the CMP
     audits are inhibited.

     Entering the command 700 generates the command ALW:AUD[=a],CMP=b
     and causes the indicator to return to normal video.

     The command 900 can be entered to get a ROP listing of routine
     audit status for the CMP. This command generates the message
     OP:STATUS[=a],AUD[=b],CMP=c.

     Box 01 - Auto Pump

     When the 601 command is entered, it generates the command
     INH:PUMP,CMP=a. This inhibits the automatic pump of the CMP on a
     major initialization (except UNIX RTR system level D4). This
     inhibit is phase-protected.

     The 701 command generates ALW:PUMP,CMP=a. This command must be
     entered to cancel the inhibit.

     Box 02 - Routine Maintenance

     This indicator reflects whether or not a routine maintenance
     function is inhibited.  Should routine maintenance functions be
     inhibited for an extended period of time, various system
     resource availability and consistency may be adversely affected.

     This box monitors the CMP's Generated Key Collection and
     Compression Routine inhibit status.  If the routine is
     inhibited, the description section is backlighted.

     When the 602 command is entered, the message INH:GKCCR,CMP=a is
     sent which requests that automatic executions of the Generated
     Key Collection and Compression Routine be inhibited.

     Entering command 702 generates the command ALW:GKCCR,CMP=a which
     requests that automatic periodic execution of the Generated Key
     Collection and Compression Routine be allowed.

     Box 04 - Software Checks

     This indicator reflects whether or not the AM application
     software checks are inhibited. If any software checks have been
     inhibited, the description section is backlighted.

     The command 604 generates the message INH:SFTCHK,CMP=a and 704
     generates ALW:SFTCHK,CMP=a.

     Box 05 - Alarmed Messages Discarded

     The input message CHG:MSGCNTL,CMP=a (where a is the CMP pair
     number) is associated with box 05.  This box will also backlight
     to indicate some type of alarmed messages (CRITICAL, MAJOR,
     MINOR, or MANUAL) are being discarded.

     Box 06 -  Box 06 is currently not used.

     Box 07 - Recent Change Backout

     This indicator shows the status of RC backout.  If set, RCs will
     not be reapplied following a full initialization.

     The description portion shows when the recent changes are
     actually backed out or applied.  A number indicating the status
     of a backout in progress will appear on the third line of the
     box.  From 200 down to 100 is CORC backout; 200 meaning CORC is
     still fully backed out and 100 meaning CORC is fully rolled
     forward. From 100 down to 0 is RC backout; 100 meaning RC is
     still fully backed out and 0 meaning RC is fully rolled forward.
     Recent changes can be backed out only in conjunction with a full
     initialization.

     The command 407 generates the message SET:BACKOUT,RC,CMP=a and
     507 generates CLR:BACKOUT,RC,CMP=a.

     Box 08 - Hardware Checks

     The command 208 (INH:HDWCHK,CMP=a) causes all CMP hardware
     checks to be inhibited.  The lower portion of this box is
     lighted only if all hardware checks have been inhibited.

     If hardware checks are allowed circuit by circuit, the indicator
     will not be cleared.

     The command 308 (ALW:HDWCHK,CMP=a) allows all CMP hardware
     checks. This will clear the backlighting of the box.

     Box 09 - CMP Brevity Controls

     Certain messages are normally suppressed from printing at the
     ROP. By inhibiting the controls, all CMP output messages would
     be sent to the AM regardless of past message counts. Using this
     command can increase link traffic to the AM, and thus, can be
     service affecting.

     Inhibiting the brevity controls is achieved by entering command
     609 (INH:BREVC,CMP=a).  The controls can be returned to normal
     by entering the command 709 (ALW:BREVC,CMP=a).

     Box 10 - UPD Backout

     This indicator shows whether or not recently applied CMP program
     updates are currently applied or backed out.

     The description portion shows when the program updates are
     actually backed out or applied. Program updates can be backed
     out or applied only in conjunction with a full initialization.

     There are no menu commands for this box.

     Box 11 - Min Mode

     This box is used to display whether or not the AM/CMPs are in
     minimum mode.
     The CMP 0 PRIM STAT box located in the top-middle portion of the
     screen can be updated with vartext for internal indicators.
     This box contains the following three subboxes:

       1. Top PRIM STAT box:  Left half is logical link map
          designation (0-0 or 1-0) and right half is PCD status.

       2. Middle PRIM STAT box:  Contains the following three lines
          of information:

            o  Initialization phrases and highest priority status
               phrases for PRIM CMP

            o  Initialization progress counter

            o  Initialization phrase trigger.

       3. Bottom PRIM STAT box:  Contains the following four lines:
            o  HASH ERR

            o  GEN DIFF

            o  SPEC GROW (Not Used)

            o  COMM LOST.

     The MATE STAT box, located in the lower middle portion of the
     screen, contains the following two subboxes:

       1. Top MATE STAT box:  The left half contains the logical link
          map designation (0-0 or 1-0) for the MATE CMP.  The right
          half displays the PCD status of the MATE CMP.

       2. Bottom MATE STAT box:  Contains initialization and status
          phrases for the MATE CMP.

     Figure .AW G303/ shows an example of the 1850 display page.

     Any available paging command can be entered from the 1850
     display page.

     All 600 and 700 level pokes are duplex commands which can only
     be entered from the primary (PRIM) CMP page (1850).

 2
     CMD   RESULT

     208   Inhibits hardware checks of CMP
           (INH:HDWCHK,CMP=a,PRIM)
     308   Allows hardware checks of CMP
           (ALW:HDWCHK,CMP=a,PRIM)
     407   Backout uncommitted recent changes of CMP
           (SET:BACKOUT,RC,CMP=a,PRIM)
     507   Clears recent changes from a CMP
           (CLR:BACKOUT,RC,CMP=a,PRIM)
     600   Audit cycle inhibited for CMPs
           (INH:AUD[=a],CMP=b)
     601   Inhibits automatic pump of CMPs on full initialization
           (INH:PUMP,CMP=a)
     602   Routine maintenance is inhibited; specifically, Generated
           Key Collection and Compression Routine for CMPs (INH:GKCCR,CMP=a)
     604   Inhibits software error checks of CMPs
           (INH:SFTCHK,CMP=a)
     609   Inhibits automatic brevity control for CMPs
           (INH:BREVC,CMP=a)
     700   Audit cycle allowed for CMPs
           (ALW:AUD[=a],CMP=b)
     701   Allows automatic pump of CMPs
           (ALW:PUMP,CMP=a)
     702   Routine maintenance is allowed; specifically, Generated
           Key Collection and Compression Routine for CMPs (ALW:GKCCR,CMP=a)
     704   Allows software error checks in CMPs
           (ALW:SFTCHK,CMP=a)
     709   Allows automatic brevity control for CMPs
           (ALW:BREVC,CMP=a)
     800   Requests off-normal reports for CMP status
           (OP:SYSSTAT,CMP=a)
     900   Requests audit status for CMP
           (OP:STATUS[=a],AUD[=b],CMP=c,PRIM)
     919   Requests purging initialization of selected CMP
           (INIT:CMP=a,PRIM,PGI)
     920   Requests selective initialization of selected CMP
           (INIT:CMP=a,PRIM,SI)
     922   Requests full initialization of selected CMP
           (INIT:CMP=a,PRIM,FI)
     923   Requests full initialization and pump of selected CMP
           (INIT:CMP=a,PRIM,FI,PUMP)


     The 1851 page is similar to the 1850 except that 600 and 700
     level pokes cannot be entered from the 1851 page.  Also, the
     1851 page has the 930 and 931 commands that the 1850 does not
     have.

     The 1851 page provides status displays for both the primary and
     mate CMP pair.  Also provided are menu commands to inhibit or
     allow hardware and software checks, routine audits, automatic
     pump, brevity control, and set and clear for recent change
     backout.  Requests for full initialization can be poked from the
     1851 page.
     On the 1851 page display, each processor is identified by its
     CMP pair number and by its physical representation which
     includes the message switch side.  There will be only one
     primary/mate CMP pair (0) for 5E6 and later.

     During CMP initialization, the initialization status phrase
     progress marks will be displayed in the PRIM STAT portion of the
     screen along with the progress counter which shows the progress
     within a particular phase of the initialization.  The set of
     progress marks used will be different from the set used for the
     SMs pump and initialization sequences on MCC Page 1800,X.

     Table .AW TAM/ shows the CMP Off-Normal Status Phrases along with the
     priority, color, and an explanation of each.

     After initialization has completed, the current (highest) level
     CMP status will be displayed (just as with the SMs on the 1800,X
     page).  A ``+'' sign at the end of the status phrase indicates
     that more than one off-normal status exists.  The OP:SYSTAT
     input message or 800 poke command can be used to obtain
     additional off-normal status information.  Also, the current
     (highest) status of the primary CMP will be displayed.
     Additional status phrases are displayed in the other PRIM STAT
     and MATE STAT boxes along with the PCD status.

     Some of the boxes on the 1851 page have numbers at the bottom.
     These numbers show what commands are available from the display.
     For example, at the bottom of Box 00 the number ``9'' appears.
     The ``9'' means output is available by entering 900.  On color
     MCC terminals, there is also color mapping from the commands
     shown on the left of the display to the numbers in the boxes.
     This section describes the individual indicators and their
     behavior.

     Box 00 - Routine Audits

     This indicator shows if the automatic execution of the CMP audit
     cycle is inhibited.

     The command 900 can be entered to get a ROP listing of routine
     audit status for the CMP. This command generates the message
     OP:STATUS[=a],AUD[=b],CMP=c.

     Box 01 - Auto Pump

     Commands to allow or inhibit automatic pump of the CMP must be
     entered from Page 1850.

     Box 02 - Routine Maintenance

     This indicator reflects whether or not a routine maintenance
     function is inhibited.  Should routine maintenance functions be
     inhibited for an extended period of time, various system
     resource availability and consistency may be adversely affected.

     This box monitors the CMP's Generated Key Collection and
     Compression Routine inhibit status.  If the routine is
     inhibited, the description section is backlighted.

     Commands to allow or inhibit routine maintenance functions of
     the CMP must be entered from Page 1850.

     Box 03 -   Box 03 currently is not used.

     Box 04 - Software Checks

     Commands to allow or inhibit software checks of the CMP must be
     entered from Page 1850.

     Box 05 - Alarmed Messages Discarded

     The input message CHG:MSGCNTL,CMP=a (where a is the CMP pair
     number) is associated with box 05.  This box will also backlight
     to indicate some type of alarmed messages (CRITICAL, MAJOR,
     MINOR, or MANUAL) are being discarded.

     Box 06 -  Box 06 is currently not used.

     Box 07 - Recent Change Backout

     This indicator shows the status of RC backout.  If set, RCs will
     not be reapplied following a full initialization.

     The description portion shows when the recent changes are
     actually backed out or applied.  If the backout is in progress,
     a number will appear on the third line of the box showing the
     progress of the backout. From 200 down to 100 is CORC backout;
     200 meaning CORC is still fully backed out and 100 meaning CORC
     is fully rolled forward. From 100 down to 0 is RC backout; 100
     meaning RC is still fully backed out and 0 meaning RC is fully
     rolled forward.  The RCs can be backed out only in conjunction
     with a full initialization.

     The command 407 generates the message SET:BACKOUT,RC,CMP=a and
     507 generates CLR:BACKOUT,RC,CMP=a.

     Box 08 - Hardware Checks

     The command 208 (INH:HDWCHK,CMP=a) causes all CMP hardware
     checks to be inhibited.

       Note:   The lower portion of this box is lighted only if
               all hardware checks have been inhibited.

     If hardware checks are allowed circuit by circuit, the indicator
     will not be cleared.

     The command 308 (ALW:HDWCHK,CMP=a) allows all CMP hardware
     checks. This will clear the backlighting of the box.

     Box 09 - CMP Brevity Controls

     Commands to allow or inhibit brevity control must be entered
     from Page 1850.

     Box 10 - UPD Backout

     This indicator shows whether or not recently applied CMP program
     updates are currently applied or backed out.

     The description portion shows when the program updates are
     actually backed out or applied. Program updates can be backed
     out or applied only in conjunction with a full initialization.

     There are no menu commands for this box.

     Box 11 - Min Mode

     This box is used to display whether or not the AM/CMPs are in
     minimum mode.
     The MATE STAT box located in the top-middle portion of the
     screen can be updated with vartext for internal indicators.
     This box contains the following three subboxes:

       1. Top MATE STAT box:  Left half is logical link map
          designation (0-0 or 1-0) and right half is PCD status.

       2. Middle MATE STAT box:  Contains the following three lines
          of information:

            o  Initialization phrases and highest priority status
               phrases for MATE CMP

            o  Initialization progress counter

            o  Initialization phrase trigger.

       3. Bottom MATE STAT box:  Contains the following five lines:
            o  HASH ERR

            o  GEN DIFF

            o  SPEC GROW (Not Used)

            o  COMM LOST

            o  INIT PEND.

     The PRIM STAT box, located in the lower middle portion of the
     screen, contains the following two subboxes:

       1. Top PRIM STAT box:  The left half contains the logical link
          map designation (0-0 or 1-0) for the PRIM CMP.  The right
          half displays the PCD status of the PRIM CMP.

       2. Bottom PRIM STAT box:  Contains initialization and status
          phrases for the PRIM CMP.

     Figure .AW G304/ shows an example of the 1851 display page.

     Any available paging command can be entered from the 1851
     display page.

 2
     CMD   RESULT

     208   Inhibits hardware checks of CMP
           (INH:HDWCHK,CMP=a,MATE)
     308   Allows hardware checks of CMP
           (ALW:HDWCHK,CMP=a,MATE)
     407   Backout uncommitted recent changes of CMP
           (SET:BACKOUT,RC,CMP=a,MATE)
     507   Clears recent changes from CMP
           (CLR:BACKOUT,RC,CMP=a,MATE)
     800   Requests off-normal reports for CMP status
           (OP:SYSTAT, CMP=a)
     900   Requests audit status for CMP
           (OP:STATUS[=a],AUD[=b],CMP=c,MATE)
     919   Requests purging initialization of selected CMP
           (INIT:CMP=a,MATE,PGI)
     920   Requests selective initialization of selected CMP
           (INIT:CMP=a,MATE,SI)
     922   Requests full initialization of selected CMP
           (INIT:CMP=a,MATE,FI)
     923   Requests full initialization and pump of selected CMP
           (INIT:CMP=a,MATE,FI,PUMP)
     930   Start off-line pump for specified mate CMP
           (ST:OPUMP,CMP=a,MATE)
     931   Stop off-line pump for specified mate CMP
           (STP:OPUMP,CMP=a,MATE)


     This subsection contains descriptions and examples of the master
     control center (MCC) page displays that were added with or
     changed with the 5E8 software release.

     Refer to Table .AW TAF/ for a complete listing of MCC page displays.
     The 107 display page provides a listing of trunk groups that
     have reached or exceeded their automatic maintenance limit
     (AML).  The AML for each trunk group is set through Recent
     Change View 5.1.
     Two counts are maintained by the 5ESS(R) switch for each trunk
     group in an office.  These counts are as follows:

       o  TG OOS:  Total number of out-of-service (OOS) members
          (individual trunks)

       o  AML OOS:  Total number of OOS members (individual trunks)
          having OOS status due to AML reasons.

     If a trunk group's AML OOS count has reached its automatic
     maintenance limit, its TG OOS count has also reached its
     automatic maintenance limit, but not vice versa.

     When a trunk group's AML is reached or exceeded by either count,
     the trunk group number will be shown on the display.  In the
     SUMMARY STATUS AREA, the CKT LIM indicator will be backlighted
     and flashing. The associated alarm level (CRITICAL, MAJOR, or
     MINOR) will also be backlighted, as applicable.

     The 107 page display lists in numerical order the number(s) of
     the first 40 trunk groups that have reached or exceeded their
     AML.  When more than 40 trunk groups have reached or exceeded
     their AML, the word ``EXCESSIVE'' will be backlighted at the
     bottom of the listing.  No trunk group numbers are shown on the
     page display if all trunk groups are normal.

       Note:   A trunk group with its AML set to 0 will not be
               included on the page display until this limit is
               actually exceeded (that is, at least one member has
               to be OOS for a trunk group to be included on the
               display).

     Figure .AW G305/ is an example of the 107 display page.  In this
     example, an excessive amount of trunk groups (more than 40) are
     OOS as reflected by the backlighted indicator ``EXCESSIVE''.  A
     MAJOR alarm condition is shown.

     Commands are provided to output listings of all trunk groups
     whose AML OOS count has reached or exceeded their respective
     AMLs and all trunk groups having an OOS member(s).

     All available paging commands can be entered from this display.

     CMD   RESULT

     900   Listing of trunk groups whose AML OOS count has reached or
           exceeded their respective AMLs is printed at the ROP
           (OP:AML[,TG=a])
           where ``a'' is a specific trunk group number.
     901   Listing of trunk groups having any OOS member(s) is printed at
           the ROP (OP:TGCNT[,TG=a]) where ``a'' is a specific trunk
           group number.

     The 109 display page provides an indication of resource or
     real-time overloads in the administrative module (AM),
     communication module processor (CMP), and SM(s) and commands to
     inhibit or allow essential service protection (ESP).
     Any AM, SM, or CMP overload conditions are shown on the 109
     display page. The SM and CMP overload information is provided on
     a summary basis.  If an SM overload occurs, the SM number and
     type will be displayed in the indicator and backlighted. If more
     than 16 SMs are in overload, a note will appear, partially
     backlighted, indicating how many SMs are overloaded.  For a
     complete list of SMs in overload, the 900 command should be
     entered.  If a CMP overload occurs, the CMP number and whether
     it is the primary (P) or mate (M) are shown.

     Details on an SM overload can be obtained by entering the
     DISPLAY SM X OVERLOAD INFO command shown on the display.
     Likewise, details on an overloaded CMP can be obtained by
     entering the DISPLAY PRIM CMP X OVERLOAD INFO or DISPLAY MATE
     CMP X OVERLOAD INFO.

     The REALTIME overload indicators will contain NONE, MINOR,
     MAJOR, or CRIT to show the severity of the overload. NONE means
     no overload exists. MINOR and MAJOR are different levels of
     real-time overloads. CRIT (critical) is only used for SMs and is
     the most severe type of overload.

     The only craft action which can be taken during overload
     conditions is to reduce or eliminate input messages/maintenance
     commands. All other actions are initiated by the system.

     For RESOURCE overloads, either NONE or the name of the resource
     will be displayed. The monitored resources are as follows:

       o  MCB - Message Control Block

       o  PCB - Process Control Block

       o  RCV - Tone Receivers (SM only)

       o  SCB - Stack Control Block

       o  TCB - Timer Control Block

       o  PKB - Packet Buffers [operator services position system
          (OSPS) SMs only]

       o  PSU - Packet Switch Unit (Packet Switching SMs only)

       o  ADB - Analog Data Block (SM only)

       o  APB - Associated Process Block (SM only)

       o  BRCSDB - Business and Residence Custom Services (BRCS) Data
          Block (SM only)

       o  CBDB - Call Buildup Data Block (SM only)

       o  CCBCOM - Channel Control Block Communication Region (SM
          only)

       o  CHDB - Channel Data Block (SM only)

       o  CLDB - Calling Leg Data Block (SM only)

       o  DALB - D-Channel Application Linkage Block (SM only)

       o  DIB - DSL Input Buffer (SM only)

       o  EDIB - Extended DSL Input Buffer (SM only)

       o  DISPDB - Display Data Block (SM only)

       o  E911DB - Enhanced 911 Data Block (SM only)

       o  MDB - Model Data Block (SM only)

       o  MSG - Message Overflow (because of PIC overload)

       o  PHDB - Path Data Block (SM only)

       o  SCMDB - Shared Call Model Data Block (SM only)

       o  TSDB - Time Slot Data Block (SM only)

       o  PSIB - X-25 Packet Switch Input Buffer (SM only)

       o  IAQ - CMP Input Queue (CMP only).

     Essential Service Protection is normally inhibited. Therefore,
     the INHIBITED text is not backlighted. When allowed, it gives
     preferential treatment to designated lines (for example,
     hospitals, police, fire departments, etc.) during periods of
     overload.

     If the network management control is on to prevent overloads in
     this office, the ``SEE PAGE 130'' indicator will appear and be
     backlighted.

     An overload will cause the OVERLOAD indicator at the top of the
     screen to backlight. The associated alarm level (CRITICAL,
     MAJOR, or MINOR) will also backlight, if applicable.

     The AM information box contains information regarding real-time
     and resource overloads in the AM.

     The information provided on Page 109 for the SMs is the SM
     number and type.  For additional information on a specific SM,
     the poke 1300,X is used (where X is the number of the SM).

     Figure  .AW G306/ shows an example of the 109 display page with
     specific AM overload information. It also shows up to 16 of the
     SMs and up to 8 of the CMPs that are in overload. The note
     EXCESSIVE is displayed and backlighted because there are greater
     than 16 SMs in overload. The actual number of SMs in overload
     (20) is displayed.

     The SM overload information shows an overload for resource
     Extended DSL Input Buffer (EDIB), a new resource for 5E8.

     Similar to the SM, the CMP has limited information provided on
     Page 109 as shown in Figure .AW G307/.  The information shown is the
     number of the CMP and whether the CMP is the primary or the
     mate.  For more specific information regarding a specific CMP,
     pokes 1370,X for the primary CMP and 1371,X for the mate CMP
     (where X is the number of the CMP) are used.

     Commands are provided to inhibit and allow ESP, to output a list
     of all SMs that are overloaded, and to obtain detailed
     information on an SM overload condition.

     In addition to these commands, any available paging command can
     be entered from Display Page 109.

      CMD     RESULT

      600     Essential Service Protection is inhibited (INH:ESP)
      700     Essential Service Protection is allowed (ALW:ESP)
      900     Output list of SMs in overload on the ROP (OP:OVRLD:ALL)
     1300,X   SM X Overload Information is displayed
     1370,X   Primary CMP X overload information is displayed
     1371,X   Mate CMP X overload information is displayed
     The 110 display page provides a list of system and AM inhibits
     and provides maintenance menu commands for selected inhibits.
     A SYSTEM inhibit applies to the AM and all SMs.  An AM inhibit
     applies only to the AM. Unless stated otherwise, all inhibit
     requests are assumed to be phase-protected.

     Each inhibit indicator on this display has three distinct
     sections: the top line, the description, and the commands-
     available line.

     The top line in each box shows the box number. This line is
     displayed in normal video, and the field to the right of the box
     number is blank unless an inhibit has been requested by the
     craft. If an inhibit has been requested, INH, SET, MON, or CHG
     is displayed to the right of the box number, as appropriate, and
     the top line is backlighted. (For the remainder of the 110
     display page description, the result of any of these operations
     is referred to as an inhibit.) The presence of this text and
     backlighting combination means the system has recorded the
     inhibit request. It does not mean the inhibit is in effect.

     Most of the inhibit/allow and set/clear commands are effective
     immediately after the request. For these cases, all areas of the
     indicator backlight together and one of the 3-character phrases
     (INH, SET, MON, or CHG) will appear. However, in a few cases,
     the status will change independent of the request. An example of
     this is shown in box 21. The behavior of each indicator is
     explained in the Indicators section on the next several
     paragraphs.

     The middle two lines of the indicator is the inhibit
     description. These two lines show the name of the inhibit as
     well as whether or not an inhibit is in effect. Inhibits can be
     caused by system or craft-initiated actions. When an inhibit is
     in effect, this section will be backlighted. In the SUMMARY
     STATUS AREA, the SYS INH indicator will be backlighted.

     The return of the top line to normal video means that a valid
     request to allow (or clear) an inhibit has been accepted. A
     valid allow request will also cause any text in the area to the
     right of the box number to be blanked.

     The last line of each indicator shows which menu commands, if
     any, are available from the display. For example, at the bottom
     of box 17 the numbers ``6 7 9'' appear. The ``6'' means this
     item can be inhibited by entering  617, the ``7'' means it can
     be allowed by entering  717, and the ``9'' designates output is
     available with  917. On color MCCs, there is also color mapping
     from the commands shown on the left of the display to the
     numbers in the boxes. Boxes without commands listed are
     inhibited only by the system or from manual action independent
     of this display page.

     Following is the correspondence between the number key and the
     action taken:

        Number   Action

          4      Set
          5      Clear
          6      Inhibit
          7      Allow
          9      Output

     This paragraph describes the individual indicators and their
     behavior.

     Box 00 - Box 00 is not currently used.

     Box 01 - Message Class Brevity Control

     This indicator shows whether or not the automatic output message
     class brevity control is inhibited. Brevity control is used to
     restrict the generation of certain application output messages
     for both the AM and equipped SMs. Inhibiting message class
     brevity control permits normally suppressed messages to go to
     the ROP or the log file.

     The message class brevity control inhibit must be entered with
     the teletypewriter (TTY) input message INH:BREVC,MSGCLS=a.
     Since a named MSGCLS is required, a menu command is not
     provided.  Inhibiting brevity control for one or more MSGCLSs
     may cause increased communication link traffic which can degrade
     call processing performance and capacity. (See AT&T 235-6s00-
     700, Input Messages Manual.) The request will display INH when
     recorded.  This inhibit will take effect immediately with the
     request.

     Entering allow command 701 generates the message
     ALW:BREVC,MSGCLS=ALL. The request will clear the text INH when
     recorded. This allow will take effect immediately with the
     request.

     This inhibit is cleared by any high-level AM initialization.

     Box 02 - Message Class Log/Print Status

     The box 02 indicates that at least one message class has the
     log/print status that is different from the backup status.

     To change the log/print status for one or all message classes,
     enter input message CHG:LPS,MSGCLS={a|ALL} with additional
     parameters.  (See AT&T 235-600-700, Input Messages Manual.)  The
     request will display CHG when recorded. This change will take
     effect immediately with the request.

     Entering the menu command 902 generates the input message
     OP:LPS,MSGCLS=ALL and causes the status of the message classes
     to be printed at the ROP.

     Box 03 - MDII Reporting

     The machine-detected interoffice irregularity (MDII) indicator
     is backlighted when one or more MDIIs are inhibited. The
     inhibits are generated by the TTY input message INH:MDII with
     additional parameters. When the inhibit is invoked, it
     suppresses the printing of MDIIs for the trunk group(s)
     specified by the input message. The request will display INH
     when recorded. This inhibit will take effect immediately with
     the request.

     Entering the 903 command generates the message OP:MDII, which
     causes a listing of all suppressed trunk MDIIs to be printed at
     the ROP.

     Box 04 - Manual Recent Change

     This indicator shows whether or not manual entering of recent
     changes is inhibited.

     When the command 604 is entered, the message INH:RC is
     generated. The request will display INH when recorded. This
     inhibit will take effect immediately with the request.

     The allow command 704 generates the message ALW:RC. The request
     will clear the text INH when recorded.

     Since the Automatic Customer Station Rearrangement (ACSR)
     feature depends upon Recent Change, if Recent Change is
     inhibited, ACSR is also inhibited.  During manual inhibits of
     Recent Change, the RC box (box 04) is lighted and the CORC box
     (box 05) is partially lighted.

     Box 05 - Customer-Originated Recent Change (CORC)

     The box 05 indicator shows whether CORCs are inhibited.

     Box 05 is shared by CORCs and the ACSR feature.  Since the ACSR
     feature depends upon Recent Change, if Recent Change is
     inhibited, ACSR is also inhibited.  During manual inhibits of
     Recent Change, the RC box (box 04) is lighted and the CORC box
     (box 05) is partially lighted.

     When a 905 command is entered, ACSR queuing is inhibited and
     CORCs are allowed.

     Box 06 - Recent Change Logging

     The box 06 indicator shows whether or not the logging of
     manually entered recent changes for all processors is inhibited.
     This does not include customer-originated recent changes. Recent
     Change logging may be inhibited in the event logging is causing
     a problem, thereby allowing recent changes to be entered.
     Unlogged changes are lost after a boot.

     Entering the command 606 generates the message INH:RCLOG. The
     request will display INH when recorded. This inhibit will take
     effect immediately with the request.

     Entering the command 706 generates the message ALW:RCLOG. The
     request will clear the text INH when recorded.

     Box 07 - Box 7 is not currently used.

     Box 08 - Communication Link Normalization

     If a fault occurs in one or more SM communication links, the
     system will automatically try to restore the link(s) on a
     periodic basis. This inhibit will suppress this action when
     active.

     Entering command 608 will generate the message INH:CLNORM. The
     request will display INH when recorded. This inhibit will take
     effect immediately with the request.

     When the command 708 is entered, it generates the message
     ALW:CLNORM. The request will clear the text INH when recorded.

     Since attempts to restore CLNKS are periodic, there may be a
     delay from the time an allow or inhibit request is recorded
     until the allow or inhibit is recognized.

     Box 09 - Centralized Automatic Message Accounting (CAMA)
     Suspension

     The box 09 indicator shows whether or not calls are being routed
     through the CAMA operator number identification (ONI) process
     for billing.  Since inhibiting this indicator causes lost
     revenue, a minor alarm is sounded when the inhibit is invoked.

     Entering the command 609 generates the message INH:CAMAONI. The
     request will display INH when recorded. This inhibit will take
     effect immediately with the request.

     Entering the command 709 generates the message ALW:CAMAONI. The
     request will clear the text INH when recorded.

     Box 10 - Trunk Hold

     The box 10 indicator shows whether or not one or more trunk
     groups are being monitored.

     To monitor one or more trunk groups, the input message MON:TRUNK
     must be entered. The request will display MON when recorded.
     This monitoring will take effect immediately with the request.

     The system looks for stop-go signaling failures in members of
     monitored group(s). If a failure occurs, the member is held
     off-hook and out of service for the craft to determine the
     nature of the failure.

     The input message CLR:TRUNK is entered to remove the stop-go
     signaling.

       Warning:   This message will return all members back to
                  service, even if they failed.  The request will
                  clear the text MON when recorded.

     Entering the 910 command generates the input message OP:TRUNK,
     which causes a listing of all trunk groups and members being
     monitored to be printed at the ROP.

     Boxes 11 Through 15 -  Boxes 11 through 15 are not currently
     used.

     Box 16 - Routine Audits

     The box 16 indicator shows if the automatic routine execution of
     one or both AM application audit cycles (OKP or SMKP) are
     inhibited.

     The only way to obtain a single audit inhibit is via a TTY input
     message in the message mode. (See INH:AUD=a,ENV=b in AT&T 235-
     600-700, Input Messages Manual.) Single inhibits are not phase-
     protected.

     Entering the 616 command requests the inhibit of all audits and
     generates the message INH:AUD=CYCLE,ENV. The request will
     display INH when recorded. The request state does not
     necessarily imply that the inhibit is in effect. Normally, the
     status will follow the request within a short period of time.

     If the 716 command is entered, the message ALW:AUD=CYCLE,ENV is
     sent. The request will clear the text INH when recorded. The
     request state does not necessarily imply that the inhibit has
     been cleared. Normally, the status will follow the request
     within a short period of time.

     The command 916 (OP:AUD,STATUS=ALL,ENV=a) can be entered to get
     the ROP listing of routine audit status for the application AM.

     Box 17 - CM Routine Exercises

     The box 17 indicator shows if any or all of the application
     routine hardware exercises are inhibited in the communication
     module (CM).  Inhibits for routine exercises are effective for
     only one exercise session. If the tests are in progress when the
     message is received, the inhibit will not take place until the
     next session.

     Routine exercises are scheduled to run at specific times (for
     example, daily at midnight). If inhibited exercises are allowed
     after the scheduled time, the exercises are not started until
     the next scheduled session.

     When 617 is entered, the message INH:REX,CM is generated, which
     inhibits all application CM routine exercises. The request will
     display INH when recorded. This inhibit will take effect
     immediately with the request.

     If the command 717 is entered, the message ALW:REX,CM is
     generated, which allows all application CM routine exercises.
     The request will clear the text INH when recorded.

     Entering the command 917 sends the message OP:REXINH,CM, which
     generates a status listing at the ROP.

       Note:   These are application routine exercises and are
               different from the routine exercises for the AM, as
               shown on the EAI display.

     Box 18 - Software Checks

     The box 18 indicator reflects whether or not the AM application
     software checks have been inhibited. The AM software checks and
     the application software checks are different, but are
     controlled together from manual commands.

     The box 18 indicator can only be controlled from the EAI or TTY
     input message INH:SFTCHK.  This inhibit will prevent internal
     software checks from causing initializations.

     Entering the 618 command requests the inhibit of internal
     software checks and generates the message INH:SFTCHK.  The
     request will display INH when recorded.  The request state does
     not necessarily imply that the inhibit is in effect.  Normally
     the status will follow the request within a short period of
     time.

     If the status is inhibited without being requested, the inhibit
     was automatically applied by the system.

     If the 718 command is entered, the message ALW:SFTCHK is sent.
     The request will clear the text INH when recorded.

     Box 19 - Min-Mode

     The box 19 indicator shows the states of application min-mode.
     When this box is backlighted, no call processing functions are
     allowed in the AM. This is only used in extreme emergencies to
     prevent customer actions from interfering with machine
     operations.

     Min-mode is invoked and deleted via EAI application pokes ``M''
     and ``N,'' respectively.

     The request will display INH when recorded. This inhibit will
     take effect immediately with the request following the next
     major AM initialization.

     The request will clear the text INH when recorded and take
     effect on the next major AM initialization.

     Box 20 - Message Brevity Control

     The box 20 indicator gives inhibit status of message brevity
     control for all messages originating from the application
     processes in the AM only.

     Entering inhibit command 620 generates the message INH:BREVC,AM.
     The request will display INH when recorded. This inhibit will
     take effect immediately with the request.

     Entering the allow command 720 generates ALW:BREVC,AM. The
     request will clear the text INH when recorded.

     This inhibit is cleared by any high-level AM initialization.

     Box 21 - Recent Change Backout

     The box 21 indicator shows whether or not uncommitted (recently
     entered) AM recent changes are loaded or backed out. Backout can
     only occur as a result of an AM high-level initialization.

     The description portion shows when the recent changes are
     actually backed out or loaded. If the backout is in progress, a
     number will appear on the third line of the box showing the
     progress of the backout. From 200 down to 100 is CORC backout;
     200 meaning CORC is still fully backed out and 100 meaning CORC
     is fully rolled forward. From 100 down to 0 is RC backout; 100
     meaning RC is still fully backed out and 0 meaning RC is fully
     rolled forward. Recent changes can be backed out only in
     conjunction with a high-level initialization.

     Recent changes should be backed out if a recent change is
     suspected to be the cause of an AM performance problem.

     When the command 421 is entered, the message SET:BACKOUT,RC,AM
     is generated. The request will display SET when recorded. The
     request state does not necessarily imply that the set is in
     effect.

     When the command 521 is entered, the message CLR:BACKOUT,RC,AM
     is sent. The request will clear the text SET when recorded. The
     request state does not imply that the backout has been cleared.

     Box 22 - Emergency Action Interface/Miscellaneous Checks

     The box 22 indicator shows if Emergency Action
     Interface/Miscellaneous checks are inhibited.  This box includes
     hardware and error interrupts inhibits from the Emergency Action
     Interface page and also error source inhibits.

     When one of the messages INH:ERRINT or INH:ERRSRC is input, it
     will cause the box to backlight.  This box will also backlight
     if error interrupt is inhibited on the Emergency Action
     Interface page.  Input messages ALW:ERRINT or ALW:ERRSRC will
     allow the respective inhibits.  Effective with the 5E8 software
     release, the lower portion of this box is lighted if any error
     interrupt inhibits have been inhibited or error source inhibits
     are inhibited.  If error interrupt checks are allowed unit by
     unit, the indicator will not be cleared until the last unit is
     allowed.

     When the command 922 is entered, the message OP:ERRCHK is sent.
     This generates a listing of the active inhibits.

     Box 23 - Routine Maintenance

     This indicator reflects whether or not a routine maintenance
     function is inhibited.  Should routine maintenance functions be
     inhibited for an extended period of time, various system
     resource availability and consistency may be adversely affected.

     This indicator monitors the AM's Generated Key Collection and
     Compression Routine inhibit status.  If the routine is
     inhibited, the description is backlighted.

     When the 623 command is entered, the message INH:GKCCR,AM is
     sent which requests that automatic executions of the Generated
     Key Collection and Compression Routine be inhibited.

     Entering command 723 generates the command ALW:GKCCR,AM which
     requests that automatic periodic execution of the Generated Key
     Collection and Compression Routine be allowed.

     Box 24 - Hardware Checks

     The box 24 indicator shows whether or not the AM/CM application
     hardware checks have been inhibited.  This indicator can only be
     controlled from the EAI or by TTY input message INH:HDWCHK.
     This inhibit will prevent maskable hardware faults from causing
     recovery.

     Entering the 624 command requests the inhibit of maskable
     hardware faults and generates the message INH:HDWCHK.  The
     request will display INH when recorded.  The request state does
     not necessarily imply that the inhibit is in effect, since the
     status will follow the request within a short period of time.

     If the status is inhibited without being requested, the inhibit
     was automatically applied to the system.

     When the 724 command is entered, the message ALW:HDWCHK is sent.
     The request will clear the text INH when recorded.

     Box 25 - AM Routine Exercises

     The box 25 indicator shows if any or all of the application
     hardware routine exercises are temporarily inhibited in the AM.

     Entering the 925 command sends the message OP:REXINH,AM which
     generates a status listing of temporary AM REX inhibits to be
     printed at the ROP.  Temporary AM REX inhibits are not preserved
     after a level 3 or level 4 AM initialization.

     Entering the 925,PERM command sends the message
     OP:REXINH,AM,PERM which generates a status listing of permanent
     AM REX inhibits to be printed at the ROP.  Permanent AM REX
     inhibits are preserved through any level (1-4) of AM
     initialization.

     Boxes 26 and 27 -  Boxes 26 and 27 are not currently used.

     Figure .AW G308/ is an example of the 110 page display.  The MANUAL RC
     (box 04), REX CM (box 17), and REX AM (box 25) are inhibited.
     The RC BACKOUT (box 21) is currently set and is partially backed
     out (80%). However, the top line is normal video, and there is
     no SET text after the 21. This indicates that the craft does not
     desire the recent changes to be kept out.

     In addition to the following commands, all available display
     commands can be accessed from Display Page 110.
 2

       CMD      RESULT

       421      RC Backout (AM) is set (SET:BACKOUT,RC,AM)
       521      RC Backout (AM) is cleared (CLR:BACKOUT,RC,AM)
       604      Manual RC is inhibited (INH:RC)
       606      RC Logging is inhibited (INH:RCLOG)
       608      CLNK Normalization is inhibited (INH:CLNORM)
       609      CAMA is inhibited (suspended) (INH:CAMAONI)
       616      Routine Audits (AM) are inhibited (INH:AUD=CYCLE,ENV)
       617      Routine Exercises (CM) are inhibited (INH:REX,CM)
       618      Internal Software Checks are inhibited (INH:SFTCHK)
       620      Message Brevity Control (AM) is inhibited (INH:BREVC,AM)
       623      Routine Maintenance (AM) is inhibited; specifically,
                Generated Key Collection and Compression Routine
                (INH:GKCCR,AM)
       624      Internal Hardware Checks are inhibited (INH:HDWCHK)
       701      Message Class Brevity Control is allowed
                (ALW:BREVC,MSGCLS=ALL)
       704      Manual RC is allowed (ALW:RC)
       706      RC Logging is allowed (ALW:RCLOG)
       708      CLNK Normalization is allowed (ALW:CLNORM)
       709      CAMA is allowed (no longer suspended) (ALW:CAMAONI)
       716      Routine Audits (AM) are allowed (ALW:AUD=CYCLE,ENV)
       717      Routine Exercises (CM) are allowed (ALW:REX,CM)
       718      Internal Software Checks are allowed (ALW:SFTCHK)
       720      Message Brevity Control (AM) is allowed (ALW:BREVC,AM)
       723      Routine Maintenance (AM) is allowed; specifically,
                Generated Key Collection and Compression Routine
                (ALW:GKCCR,AM)
       724      Internal Hardware Checks are allowed (ALW:HDWCHK)
       902      Message Class Log/Print Status is output (OP:LPS<MSGCLS=ALL)
       903      MDII Report is output (OP:MDII)
       905      CORC Status is output (OP:STAT,CORC,ACSR)
       910      Trunk Hold list is output (OP:TRUNK)
       916      Routine Audits (AM) are output (OP:AUD,STATUS=ALL,ENV)
       917      Routine Exercises (CM) are output (OP:REXINH,CM)
       922      Listing of active inhibits is output (OP:ERRCHK)
       925      Temporary Routine Exercises inhibits (AM) are output
                (OP:REXINH,AM)
     925,PERM   Permanent Routine Exercises inhibits (AM) are output
                (OP:REXINH,AM,PERM)


     The purpose of the 115 display page is to provide a summary of
     off-normal status for the hardware units and links which support
     AM to SM(s) communication and provide paths for all circuit
     switched calls.
     The 115 display page has two separate and distinct versions.
     The first version (Figure .AW G309/) is for offices with communication
     module model 2 (CM2) hardware. The second version (Figure .AW G310/)
     is for offices with CM1 hardware.

     The 115 page provides overall status for MSGS 0, MSGS 1, MI/NC 0
     (MI/LI/NC 0 for CM1), MI/NC 1 (MI/LI/NC 1 for CM1), TMS 0, TMS
     1, communication links for the SMs, fan and fan fuse alarms for
     the ONTCs (for the MSGSs and TMSs for CM1), the status of the
     hardware check inhibit request bit, and the status of the
     MI/NC/TMSs (MI/LI/NC/TMSs for CM1) functioning as a group
     (ONTCCOM).

     The ONTCCOM 0 includes MI 0 (and LI 0 in CM1), NC 0, and TMS 0.
     The ONTC 0 includes ONTCCOM 0 and all DLIs on side 0.  The
     ONTCCOM 1 includes MI 1 (and LI 1 in CM1), NC 1, and TMS 1.  The
     ONTC 1 includes ONTCCOM 1 and all DLIs on side 1.

     If an MSGS, MI/NC (MI/LI/NC in CM1), or TMSLNK has an off-normal
     condition such as out-of-service (not family of equipment),
     unavailable, hardware checks inhibited, etc., the appropriate
     indicator giving the MCC page to see for detailed information is
     backlighted. The phrase ``SEE PAGE XXXX IF BACKLIT'' is
     backlighted when any of the boxes are backlighted to point out
     that the numbers in the boxes are the page numbers to request.

       Note:   The 1210 boxes are backlighted only for NC
               reference or oscillator problems.

     The CLNKS indicator is a summary of the equipped SM
     communication links status which is detailed on Page 1260.

     The CLNKs are not TMSLNKs.  A CLNK is a communication path
     between the AM and an SM which passes through an MSCU, MMP, TMS,
     TMSLNK, and DLI.  The TMSLNKs connect the TMS to the DLI.

     The backlighted indicator identifies the page necessary for
     acting on the problem. As an example, the box with 1242
     indicated is backlighted in Figure .AW G309/ because a module message
     processor (MMP) on Display Page 1242 is shown as out of service
     (OOS).  The MMP out of service is also reflected on the MSGS 0
     Page 1240, but going to 1240 would not be the final step to see
     and act on the problem so the MSGS 0 box with 1240 indicated is
     not backlighted. If a foundation peripheral controller (FPC) or
     pump peripheral controller (PPC) was out of service also, then
     the MSGS 0 box would backlight as shown in Figure .AW G310/. The
     purpose of this strategy is to get the craft directly to the
     problem with minimum paging.  Therefore, if the 1240 (MSGS 0)
     box and the 1241 (or 1242) were both backlighted, an out of
     service (not family of equipment), an unavailable, an out-of-
     service power, or an unavailable power condition would exist in
     an MMP and an FPC, PPC, or MSCU.

     The TMS 0 and 1 boxes (indicating Page 1220) will never
     backlight. If a TMS is OOS, it would be due to the whole ONTC
     being OOS or UNV; therefore, 1209 is the appropriate page to
     display.

     Effective with the 5E8 software release, AM and CM hardware
     check inhibits have been separated.  The system will not
     implicitly set CM hardware check inhibits when AM hardware check
     inhibits are requested.  The indicator CM HDWCHK INH REQ only
     appears on the page display if the data delivery request
     automatic CM hardware check bit is set due to automatic
     escalation or manual request.  Presence of the indicator means
     that there is a global inhibit request for all CM hardware
     checks.  This bit can be set manually by entering the input
     message INH:HDWCHK,CM or by setting the application parameter to
     `` f '' (or ``F'') on the EAI page.  The bit can be cleared by
     entering input message ALW:HDWCHK,CM or by resetting the
     application parameter to ``g'' (or ``G'') on the EAI page.
     Allowing hardware checks on all CM units individually will not
     clear the bit, and the global indicator will remain on the page.
     This means that at the next CM initialization, all CM
     application hardware checks will be inhibited.

     The CM isolation is available only in the CM2 version of Page
     115.  The indicator REQ CM ISOL appears on the page display to
     signal that manual CM isolation has been requested.  A separate
     indicator, CM ISOL, is displayed when CM isolation is in effect.

     Figure .AW G309/ shows an example of the CM2 Version with problems in
     MI/NC 1, MSGS 0, TMS 0, CLNKS, and ONTC 1.  Further information
     on these problems would be found on display 1210 - MI/NC 0 & 1,
     1242 - MSGS 0 - COMMUNITIES 2 - 7, 1221 - TMS 0 TMS LINKS 002 -
     063, 1260 - CLNK SUMMARY, and 1209 - ONTC 0 & 1. There is a fan
     alarm on ONTC 0 and the ONTC 1 fan fuse alarm is inhibited.  The
     CM ISOL indicator shows that CM isolation is in effect.  Also,
     CM HDWCHK INH REQ appears which signals that CM hardware check
     inhibits have been requested.

     Figure .AW G310/ shows an example of the CM1 Version with problems in
     MI/LI/NC 1, MSGS 0, TMS 0, CLNKS, and ONTC 0.  Further
     information on these problems would be found on displays 1210 -
     MI/LI/NC 0 & 1, 1240 - MSGS 0 SUMMARY, 1221 - TMS 0 - TMS LINKS
     002 - 063, 1260 - CLNK SUMMARY, and 1209 - ONTC 0 & 1. There is
     a fan alarm on MSGS 0, and the TMS 0 fan fuse alarm is
     inhibited.  The FPC DPLF indicator shows that duplex failure is
     in effect.

     There are no menu commands on the 115 display page. Commands for
     removing, restoring, diagnosing, etc., are listed on the related
     pages. There are no menu commands on the displays for fans or
     fan fuses. For fans or fan fuses, see CLR:FANALM in AT&T 235-
     600-700, Input Messages Manual.

     All available display commands can be entered from the 115
     display page.
     The purpose of the 123 display page is to provide status and
     maintenance commands for two DFCs and up to 16 moving head disks
     (MHD).  It also provides status and commands for disk
     independent operation when both essential disks are lost.  In
     5E5 and later software releases, the 123 display page provides
     status of the Auto MHD Configuration feature.

     If there are more than two DFCs in the system, a second DFSA
     page (Page 125) is used.  The format of the 125 page is the same
     as the 123 except the AUTO MHD CONFIGURATION status is not
     shown; it appears only on Page 123.
     The 123 page has three separate and distinct functions.

     The first function of this page is to provide status and
     maintenance commands for DFCs 0 and 1 and associated MHDs (up to
     16).  If the system is equipped with SCSI, this page also
     provides status and maintenance commands for SBUSes (up to 4).

     The second function is to provide status and commands during
     disk independent operation (DIOP).  When both of the MHDs that
     are marked E (essential) go out of service, this page is
     automatically displayed.  This is called full DIOP.  The
     appropriate menu commands to use under these circumstances are
     the 600 series of commands.  When in full DIOP (Figure .AW G312/), a
     620 command will appear which will allow the MHD to be reloaded
     from tape without bringing down call processing during the
     reading of the tape.  When the MHD has been reloaded, a minimum
     of a 52 boot is required.  The other 600 series commands, with
     the exception of the 699 poke, may be used also when not in
     DIOP.  The 699 poke works only in full DIOP.  Effective in 5E7,
     both the 602 poke to restore the DFC controller and the 604 poke
     to restore the SBUS controller require UCL when the system is in
     full DIOP.  These pokes (602/604) will not restore associated
     subunits (MHDs) to prevent accidental disk restoral during disk
     maintenance.

     If only one of the essential MHDs goes out of service, the MHDs
     are in simplex operation (Figure .AW G311/), but the page is not
     automatically displayed.

     During full DIOP, the area at the bottom of the page between the
     two horizontal lines will display output messages for the 600
     series menu commands.

     The third function of the 123 page, in 5E5 and later software
     releases, is to provide for the display of the Automatic MHD
     Configuration feature.  The AUTO MHD CONFIGURATION  data
     displayed on 123 page is a summary status of information from
     Pages 178, Auto Spare Disk, and 179, Disk Configuration.

     Possible values of the Automatic MHD Configuration feature are
     as follows:

       a. AUTO MHD CONFIGURATION READY:  The feature is armed and
          ready to run if needed.

       b. SEE PAGE 179, CONFIG MHDs ...:  The listed MHDs have been
          reconfigured; see Page 179 for more data.

       c. AUTO MHD CONFIGURATION OFF:  The feature is turned off.

       d. MHD CONFIG INHIBITED, SEE PAGE 178:  The feature is blocked
          on one or more MHDs or the entire office; see Page 178 for
          more data.

       e. MHD CONFIG IN PROGRESS, SEE PAGE 178:  An MHD configuration
          is in progress; see Page 178 for more data.

     There are two columns of notations on the right side of each of
     the MHD status columns.  The first of the two columns contains
     one of the following two letters:

       o  Y - (Yes):  This means the MHD was diagnosed or restored
          since the last system initialization and appears to be
          usable.

       o  N - (No):  This means the MHD was not diagnosed or restored
          since the last system initialization and does not appear to
          be usable.

     The second column contains the letter E which signifies that the
     associated MHD is essential.

     The upper two display fields, OPTION LEVEL and CURRENT LEVEL,
     inform the user of the optional disk independent operation
     feature level selected for the operating system and the current
     disk independent operation state the operating system is in.

     The OPTION LEVEL displayed will be one of the following:

       o  NODIOP:  Disk independent operation feature is not
          selected.

       o  DIOP:  Conditional disk independent operation is selected.

       o  UCLDIOP:  Unconditional disk independent operation is
          selected.

     The CURRENT LEVEL displayed will be one of the following:

       o  NORMAL:  Normal operating system without disk independent
          operation mode.

       o  SIMPLEX:  Operating system running with at least one
          essential MHD out of service.

       o  DUPLEX:  Operating system is running with all duplex
          essential MHDs active.

       o  CONDITIONAL DIOP:  Operating system is in conditional disk
          independent operation  mode with the last remaining duplex
          essential MHD about to be removed from service.

       o  FULL DIOP:  Operating system is running with a duplex
          essential pair of MHDs out of service.

     For each unit displayed, the following information is shown:

       o  Major state of the unit

       o  Minor state of the unit (if available)

       o  Usability of the unit (Y = usable, N = unusable)

       o  Essential status of the unit (E = essential, M = manually
          nonremovable, blank = nonessential)

       o  Microcode status (Firmware of Pumpcode) for the DFC

       o  Overload status of a DFC.

     Figure .AW G311/ shows the simplex version of the disk file system
     access page for an office with SMD only.  In this example, one
     of the essential MHDs (MHD 1) is OOS, so the current level is
     marked as SIMPLEX. The OOS MHD caused the AM PERPH indicator at
     the top of the page to be backlighted.  The automatic MHD
     configuration feature is ready.

     When the simplex mode is entered, the system begins to lock
     essential, nonswappable processes from disk into core (AM
     memory).  Upon completion of the locking process, the system
     will print the message, REPT DIOP SIMPLEX PROCESSING COMPLETED.
     If the system has problems in locking the essential processes
     into core, it will print the message, REPT DIOP SIMPLEX UNSWAP
     FAILURE PID=xx (xx = utility ID of process that failed to lock
     into memory).  This message will reprint every 5 minutes until
     the locking process is completed.

     Figure .AW G312/ shows the FULL DIOP version.

     Figure .AW G313/ shows the simplex version of the disk file system
     access page for an office with SCSI only or with both SMD and
     SCSI.

     The only difference between the SCSI-DFSA and SMD-DFSA versions
     of the 123 page is the addition of ``SBUS 0 SBUS 2'' under DFC
     0, ``SBUS 1 SBUS 3'' under DFC 1 on the SCSI version, and the
     604 command for RST/RMV SBUS.

     Commands are provided to remove, restore, and diagnose the MHDs
     and to take appropriate actions on the MHDs when one or more
     essential MHDs are out of service.

     All available displays can be accessed from the 123 page.
 2

           CMD         RESULT

           2XX         MHD XX is removed from service
                       (RMV:MHD=XX)
           3XX         MHD XX is restored to service
                       (RST:MHD=XX)
           5XX         MHD XX is diagnosed
                       (DGN:MHD=XX)
     600,n [v] [s|d]   MHD n is formatted (initialized)
                       (INIT:MHD=n)
                       v=VFY. Verify option to be used (default=no verify
                       option).
                       s=Track number or range of tracks to be initialized
                       (default=all tracks).
                       d=New. The track number or range of tracks and the
                       ``d'' option can only be used for SMD MHD.
        601,n [s]      MHD n is verified
                       (VFY:MHD=n)
                       where s represents either:
                             t=XX (XX is track number or range of tracks
                             to be verified)
                             (default=all tracks for SMD MHD)
                       or
                             b=XX (XX is block number or range of blocks
                             to be verified)
                             (default=all blocks for SCSI MHD)
                       (For example: 601,0 b=80&&100 will cause the
                       VFY MHD function to be invoked for MHD 0 and will
                       verify blocks 80 through 100 for SCSI MHD.)
        602,n [u]      DFC n controller only is restored
                       u=UCL
                       (RST:DFC=n,CONT)
      603,n [t|fn]     Dump MHD n defect table
                       t=Defect table to be dumped:MFGR,COMB,TEMP,
                       ALL,(default=COMB).
                       fn=Full pathname of a file, in double quotes, that the
                       MFGR defect table is to be written to
                       (DUMP:MHD=n:DEFECT)
       604,n a [u]     RESTORE or REMOVE SBUS
                       a=``RST'' or ``RMV''
                       (RST:SBUS=n,CONT)
                       (RMV:SBUS=n)
                       u=UCL

                          Note: For SBUS RST, UCL option is required
                          in full DIOP.

           CMD         RESULT

         677,n f       Enhanced Information Report (EIR) PRINT
                       n=DFC unit number
                       f=EIR format.  Valid values are ``n''=turn off
                       EIR PRINT, ``l''=long EIR report format,
                       ``s''=short EIR report format
          6XX,h        HELP OPTION
                       Give help for 600 series commands
           688         Clears the buffer
           699         Aborts the menu command that is presently in progress

                          Note:  The 699 poke appears only while
                          the system disk is in full DIOP.  It is not
                          effective in normal or simplex modes.

       620,n td a      Loads MHD n from tape drive td using sequence a
                       td=Tape device name
                       a=BOTH,GEN,DBONLY or CONT.

                          Note:  The 620 poke appears only while
                          the system disk is in full DIOP.  It is not
                          effective in normal or simplex modes.


       Note:   The 600 series commands work while the system disk
               is in full DIOP except that pokes 602 (DFC
               controller only restore) and 604 (SBUS controller
               only restore) require UCL.

     The purpose of the 125 display page is to provide status and
     maintenance commands for two DFCs and up to 16 moving head disks
     (MHD).  It also provides status and commands for disk
     independent operation when both essential disks are lost.

     This page exists only when there are more than two DFCs in the
     system.

     The format of the 125 page is the same as the 123 except the
     AUTO MHD CONFIGURATION status is not shown; it appears only on
     Page 123.
     The 125 page has two separate and distinct functions.

     The first function of this page is to provide status and
     maintenance commands for DFCs 2 and 3 and associated MHDs (up to
     16).  If the system is equipped with SCSI, this page also
     provides status and maintenance commands for SBUSes (up to 4).

     The second function is to provide status and commands during
     disk independent operation (DIOP).  When in full DIOP, the 125
     page will be accessible.  The 620 poke (reload from tape option)
     will only work on the 123 page.  The other 600 series commands,
     with the exception of the 699 poke, may be used also when not in
     DIOP.  The 699 poke works only in full DIOP.  Effective in 5E7,
     both the 602 poke to restore the DFC controller and the 604 poke
     to restore the SBUS controller require UCL when the system is in
     full DIOP.  These pokes (602/604) will not restore associated
     subunits (MHDs) to prevent accidental disk restoral during disk
     maintenance.

     If only one of the essential MHDs goes out of service, the MHDs
     are in simplex operation (Figure .AW G314/), but the page is not
     automatically displayed.

     During full DIOP the area at the bottom of the page between the
     two horizontal lines will display output messages for the 600
     series menu commands.

     There are two columns of notations on the right side of each of
     the MHD status columns.  The first of the two columns contains
     one of the following two letters:

       o  Y (Yes):  This means the MHD was diagnosed or restored
          since the last system initialization and appears to be
          usable.

       o  N (No):  This means the MHD was not diagnosed or restored
          since the last system initialization and does not appear to
          be usable.

     The second column contains the letter E which signifies that the
     associated MHD is essential.

     Figure .AW G314/ shows the simplex version of the disk file system
     access page for an office with SMD only.  In this example, one
     of the essential MHDs (MHD 17) has gone out of service, so the
     current level is marked as SIMPLEX.  The OOS MHD caused the AM
     PERPH indicator at the top of the page to be backlighted.

     When the simplex mode is entered, the system begins to lock
     essential, nonswappable processes from disk into core (AM
     memory).  Upon completion of the locking process, the system
     will print the message, REPT DIOP SIMPLEX PROCESSING COMPLETED.
     If the system has problems in locking the essential processes
     into core, it will print the message, REPT DIOP SIMPLEX UNSWAP
     FAILURE PID=xx (xx = utility ID of process that failed to lock
     into memory).  This message will reprint every 5 minutes until
     the locking process is completed.

     Figure .AW G315/ shows the simplex version of the disk file system
     access page for an office with SCSI only or with both SMD and
     SCSI.

     The only difference between the SCSI-DFSA and SMD-DFSA versions
     of the 125 page is the addition of ``SBUS 0 SBUS 2'' under DFC
     2, ``SBUS 1 SBUS 3'' under DFC 3 on the SCSI version, and the
     604 command to RST/RMV SBUS.

     Commands are provided to remove, restore, and diagnose the MHDs
     and to take appropriate actions on the MHDs when one or more
     essential MHDs are out of service.

     All available displays can be accessed from the 125 page.

 2
           CMD         RESULT

           2XX         MHD XX is removed from service
                       (RMV:MHD=XX)
           3XX         MHD XX is restored to service
                       (RST:MHD=XX)
           5XX         MHD XX is diagnosed
                       (DGN:MHD=XX)
     600,n [v] [s|d]   MHD n is formatted (initialized)
                       (INIT:MHD=n)
                       v=VFY. Verify option to be used (default=no verify
                       option).
                       s=Track number or range of tracks to be initialized
                       (default=all tracks).
                       d=New. The track number or range of tracks and the
                       ``d'' option can only be used for SMD MHD.
        601,n [s]      MHD n is verified
                       (VFY:MHD=n)
                       where s represents either:
                             t=XX (XX is track number or range of tracks
                             to be verified)
                             (default=all tracks for SMD MHD)
                       or
                             b=XX (XX is block number or range of blocks
                             to be verified)
                             (default=all blocks for SCSI MHD)
                       (For example: 601,0 b=80&&100 will cause the
                       VFY MHD function to be invoked for MHD 0 and will
                       verify blocks 80 through 100 for SCSI MHD.)
        602,n [u]      DFC n controller only is restored
                       u=UCL
                       (RST:DFC=n,CONT)
      603,n [t|fn]     Dump MHD n defect table
                       t=Defect table to be dumped:MFGR,COMB,TEMP,
                       ALL,(default=COMB).
                       fn=Full pathname of a file, in double quotes, that the
                       MFGR defect table is to be written to
                       (DUMP:MHD=n:DEFECT)
       604,n a [u]     RESTORE or REMOVE SBUS
                       a=``RST'' or ``RMV''
                       (RST:SBUS=n,CONT)
                       (RMV:SBUS=n)
                       u=UCL

                          Note: For SBUS RST, UCL option is required
                          in full DIOP.

           CMD         RESULT

         677,n f       Enhanced Information Report (EIR) PRINT
                       n=DFC unit number
                       f=EIR format.  Valid values are ``n''=turn off
                       EIR PRINT, ``l''=long EIR report format,
                       ``s''=short EIR report format
          6XX,h        HELP OPTION
                       Give help for 600 series commands
           688         Clears the buffer
           699         Aborts the menu command that is presently in progress

                          Note:  The 699 poke appears only while
                          the system disk is in full DIOP.  It is not
                          effective in normal or simplex modes.

       620,n td a      Loads MHD n from tape drive td using sequence a
                       td=Tape device name
                       a=BOTH,GEN,DBONLY or CONT.

                          Note:  The 620 poke appears only while
                          the system disk is in full DIOP.  It is not
                          effective in normal or simplex modes.


       Note:   The 600 series commands work while the system disk
               is in full DIOP except that pokes 602 (DFC
               controller only restore) and 604 (SBUS controller
               only restore) require UCL.

     The 126 display page provides the optional disk access
     performance data for the AT&T 3B20D computer.

     There will be a maximum of two DFCs on a DFSA performance page.
     If there are more than two DFCs in the system, a second DFSA
     performance page (Page 128) is used.

     The 126 page can show either SMD-DFSA or SCSI-DFSA, depending on
     the feature option of the operational office.

     With the SCSI feature, the DFSA performance data is not
     available when the operating system is in disk independent
     operation (DIOP) mode.

     Meanings of the performance fields displayed are as follows:

       o  CMP:  Jobs completed by the DFC for the unit.  This field
          is normalized to show the number of jobs that were
          completed per second.

       o  AVG:  The average size of the jobs completed for a unit
          (number of disk blocks).

       o  MAX:  The maximum size of a job completed in a time
          interval (number of disk blocks).

     Figure .AW G316/ shows an example of the 126 display page for an
     office with SMD only.

     Figure .AW G317/ shows an example of the 126 page with mixed SMD and
     SCSI DFCs.

     The DFC fields are the sum of the individual MHD fields
     associated with the DFC.  For SCSI DFC, the SBUS fields are the
     sum of all the MHD fields associated with this SBUS.

         CMD       RESULT

     622[,s [t]]   Performance updates are displayed
                   s = number of seconds between performance updates.
                   Valid number of seconds is between 1 and 60.  Performance
                   updates will occur 20 times, then will be automatically
                   turned off.  If s is zero or is defaulted, then
                   performance updates are turned off.
                   t = number of times to repeat the performance updates.
         688       The 3-line communication area at the bottom of the page
                   is cleared.
        6XX,h      HELP OPTION
                   Give help for 600 series commands

     The 128 display page provides the optional disk access
     performance data for the AT&T 3B20D computer.

     There will be a maximum of two DFCs on a DFSA performance page.
     This page is used only when there are more than two DFCs in the
     system.

     The 128 page can show either SMD-DFSA or SCSI-DFSA, depending on
     the feature option of the operational office.

     With SCSI feature, the DFSA performance data is not available
     when the operating system is in disk independent operation
     (DIOP) mode.

     Meanings of the performance fields displayed are as follows:

       o  CMP:  Jobs completed by the DFC for the unit.  This field
          is normalized to show the number of jobs that were
          completed per second.

       o  AVG:  The average size of the jobs completed for a unit
          (number of disk blocks).

       o  MAX:  The maximum size of a job completed in a time
          interval (number of disk blocks).

     Figure .AW G318/ shows an example of the 128 display page with full
     SCSI DFCs.

         CMD       RESULT

     622[,s,[t]]   Performance updates are displayed
                   s = number of seconds between  performance updates. 
                   Valid number of seconds is between 1 and 60.  Performance
                   updates will occur 20 times, then will be automatically
                   turned off.  If s is zero or is defaulted, then
                   performance updates are turned off.
                   t = number of times to repeat the performance updates.
         688       The 3-line communication area at the bottom of the page
                   is cleared.
        6XX,h      HELP OPTION
                   Give help for 600 series commands

     The 131 page display is a menu page that contains a list of call
     trace poke commands.
     A ``SEE PAGE'' indicator on the 131 menu page shows the
     maintenance personnel which hardware call trace page (133
     through 140, 150, or 151) to access for the details of the call
     trace.

     The 131 menu page gives the user the ability to invoke a trace
     by simply entering a poke value followed by a number or a set of
     numbers.  For example, 401,2220001 where 401 is the poke for a
     utility hardware call trace with a directory number (DN),
     2220001, being the input option.

     When tracing an Integrated Services Digital Network (ISDN)
     circuit switched lines, the channel to be traced should be
     included in the input.  If no channel is specified, then the
     default action is to trace the D-channel.  See pokes 401 and 405
     for input requirements.

     The subaddress (SA) option is used to specify which subaddress
     of a DN/MLHG with multiple call appearances to trace.
     Specifying SA=ALL will result in Page 150 being populated with
     the status of all valid subaddresses for the given input.  If
     the SA option is used, the channel (CH) option must be omitted.
     The SA option is valid for voice calls on terminals which use
     subaddresses.  This includes most custom digital subscriber
     lines (DSL) and also standard Electronic Key Telephone Service
     (EKTS) lines.  To trace packet switched calls, the PKT variable
     is included in poke commands 401, 404, 405, 406, and 410.

     The call ID number (CID) option is used to specify which call on
     a standard non-EKTS DSL to trace, or to trace circuit switched
     data calls on any type terminal.  Specifying CID=ALL will result
     in Page 150 being populated with the status of all calls for the
     given input.  If the CID option is used, the channel (CH) option
     must be omitted.

     The CID and SA options are mutually exclusive.  If an incorrect
     option is used for the call type of the given input, an error
     message will be generated, and the 150 page will be populated
     with the correct information for the input DN/MLHG.  Refer to
     the 150 page for more detailed information.

     Figure .AW G319/ shows an example of the 131 page display for 5E8.

     All poke commands that appear on the 131 display page can be
     invoked by maintenance personnel, and they can also be invoked
     from any of the call trace display pages (131-140, 150, and
     151).  Refer to Page 132 - Call Trace Menu Cont. (Figure .AW G320/)
     for more call trace poke commands.  The 131 page must be used to
     access the other call trace pages from a page that is not a call
     trace page.
     Effective with the 5E5 software release, the 132 page is a
     continuation of the 131 menu page consisting of a list of call
     trace poke commands.  The 132 Hardware Call Trace page was moved
     to Page 140.
     A ``SEE PAGE'' indicator on the 132 menu page shows the
     maintenance personnel which hardware call trace page (133-140,
     150, or 151) to access for the details of the call trace.

     The 132 menu page gives the user the ability to invoke a trace
     by simply entering a poke value followed by an option or a set
     of numbers.  For example, to trace the active loop of the B1
     channel of the operator position terminal 1-135, the poke would
     be 418,1,135,loop=0,ch=B1.

     When the 440 poke is used to trace a process id, the process id
     to trace must be for either a circuit switched voice call or a
     circuit switched data call.

     Figure .AW G320/ shows an example of the 132 page display.

     All poke commands that appear on the 132 display page can be
     invoked by maintenance personnel, and they can also be invoked
     from any of the call trace display pages (131-140, 150, and
     151).  Refer to Page 131 - Call Trace Menu (Figure .AW G319/) for more
     call trace poke commands.  Also, any call trace display page can
     be accessed from the 132 display page.
     The hardware call trace page displays (133 through 138) show the
     hardware paths of calls requested to be traced.
     Call Trace Pages 133 through 138 provide a ``snapshot'' of the
     hardware and software path(s) involved with a call.  Page 133 is
     the main UTILITY CALL TRACE display.  Some calls require several
     displays, for example, a 3-way call.  A ``SEE PAGE'' indicator
     appears if more displays are involved in a particular call.

     Information collected about dynamic data structures and hardware
     paths can aid in trouble-shooting a failed call.  The software
     state, external identifier, peripheral path, and network path
     are shown for each connection of the call and are described as
     follows:

       o  Software state:  The software state represents the state of
          the call (ringing, talking, transient, etc.) as stored in
          the process control block link area (PCBLA).

       o  External identifier:  The external identifier is the
          representation of the customer and can include the
          following:

            -- Directory Number (DN)

            -- Multiline Hunt Group (MLHG) group and member

            -- Trunk (TRK) group and member

            -- Equipment Number (EN).

       o  Peripheral path:  The peripheral path displays the hardware
          path taken by the call from the peripheral unit through the
          service units to the Time Slot Interchanger (TSI).

       o  Network path:  The network path is represented by the
          Network Control and Timing (NCT) time slot connecting the
          TSI to the Time Multiplexed Switch (TMS).  The connection
          from the NCT to the TMS is shown as either a solid line,
          representing an inter-SM call, or a dotted line,
          representing an intra-SM call.

     If a call that uses an ISLU is traced, the type of circuit
     switched service (voice or data) and a B-channel identifier (B-
     1, B-2, or ON HOLD) are displayed.  The ON HOLD means that no
     B-channel is allocated for the call.

     For an OSPS call through a remote ISLU (RISLU), the connection
     via a T1 carrier between the DLTU remote (DLTUR) in the RISLU
     and the DLTU host (DLUTH) in the switch will be shown.
     Additionally, if business and residence custom services (BRCS)
     features are assigned to a DSL, the primary directory number
     (PDN), subaddress (SA), and call appearance (CA) will be
     displayed.

     Effective with the 5E8 software release, standard ISDN DSLs are
     supported.  If a standard EKTS DSL is traced, the SA and CA are
     displayed as for a custom DSL.  If a standard non-EKTS is
     traced, SA and CA do not apply.

     The Integrated Digital Carrier Unit (IDCU) is also supported for
     the 5E8 software release.  Call Trace displays the SM and IDCU
     numbers for an IDCU.

     The IDCU peripheral unit contains a time slot interchange unit
     (TSIU) which offers the ability to make connections without
     using the TSI in the SM, thus saving SM time slot resources.  A
     trace of this hairpin connection only shows the RT and the IDCU.

     The IDCU also supports the PUB43801 interface format used for
     interfacing to D4 and D5 channel banks and to Digital Access
     Cross Connect Systems (DACS).  Since these connections do not
     use an RT, RT is not shown on the trace.

     Examples of Hardware Call Trace displays are as follows:

       o  Figure .AW G321/ - Multipoint DSL to ISDN PODS

       o  Figure .AW G322/ - Analog DN to an Analog Trunk

       o  Figure .AW G323/ - Hairpinned IDCU PUB43801

       o  Figure .AW G324/ - OSPS OPT

       o  Figure .AW G325/ - RSM Inter Cluster Link (ICL)

       o  Figure .AW G326/ - Subscriber Loop Carrier to Analog IDCU DN

       o  Figure .AW G327/ - RSM to HSM.

     Refer to 131 - Call Trace Menu display (Figure .AW G319/) for the
     complete list of call traces that can be invoked (by poke
     commands) from the 133 through 138 page displays.  Also, all
     available page displays can be invoked from the 133 through 138
     page displays.
     The purpose of the 140 page display is to provide the hardware
     connections for the packet call trace and circuit switch D-
     channel call trace.
     Effective with the 5E5 software release, Page 140 is the same as
     Page 132 for the 5E4 software release.  The only difference is
     that additional displays are available for Multipoint DSLs.

       Note:   The PDB abbreviation on the 140 page display
               actually means protocol handler data bus (PHDB).
               The PDB abbreviation appears on the page display
               because an internal software process is also named
               PHDB.

     Figure .AW G328/ is an example of a circuit switched D-Channel trace
     of a Multipoint DSL.

     Figure .AW G329/ is an example of an X.75' packet switched Hardware
     Call Trace.

     Figure .AW G330/ is an example of an IDCU D-channel Hardware Call
     Trace.  The IDCU is new with the 5E8 software release.

     Refer to Page 131 - Call Trace Menu (Figure .AW G319/) and Page 132 -
     Call Trace Menu Cont. (Figure .AW G320/) for the complete list of call
     trace poke commands that can be invoked.  Also, any call trace
     page display can be accessed from the 140 menu page.
     The purpose of the 141 through 144 display pages is to provide a
     more detailed summary status of groups of 48 SMs on one display.
     Displays 141, 142, 143, and 144 are very similar. Each one can
     display summary status of up to 48 SMs. Page 141 displays status
     for SMs 1 through 48, Page 142 displays summary status for SMs
     49 through 96, Page 143 displays status for SMs 97 through 144,
     and Page 144 displays summary status for SMs 145 through 192.

     Each equipped SM has a unique indicator on these displays. Each
     indicator has the following three distinct sections:

       o  SM NUMBER: There may be gaps in SM numbering for a
          particular office.  To provide flexibility in office
          numbering schemes, the SM numbers are not necessarily
          assigned sequentially. If an SM is not equipped, it is not
          shown. An example of this is shown in the 141 page example
          (Figure .AW G331/) by the blank indicators between SM 12 and SM
          20, SM 20 and SM 24, etc.

       o  SM TYPE: There is a 3-character acronym to show how an SM
          is being used. For example, an LSM is a local switching
          module.

       o  SM STATUS PHRASE: This is a 10-character, maximum, phrase
          which describes the most significant off-normal condition
          in the SM.  During initialization, the status phrase will
          give the current initialization progress type.  Table .AW TAN/
          lists status phrases in order of priority and gives the
          color and an explanation for each phrase.  New status
          phrases for 5E8 are TMCRST and EOCRST which indicate
          restore in progress for IDCU RT Time Slot Management
          Control and IDCU RT Embedded Operations Channel,
          respectively.  For detailed information on SM progress
          markers, see AT&T 235-105-250, System Recovery.

     If more than one off-normal condition exists in an SM, a ``+''
     will appear to the right of the status phrase (SMs 1, 5, and 48
     in Figure .AW G331/).  A complete list of active off-normal conditions
     can be output via menu command 900.

     In addition to this page, the status phrase is shown on all
     per-SM pages.

     When a new alarm condition on an SM occurs, the SM indicator
     will begin flashing. The ALM RLS key will not stop the flashing.
     The color of the flashing will reflect the new alarm only if the
     newly recorded condition is of higher or equal priority to the
     previous condition. To stop the flashing, the craft should
     display the 1010 page for that SM. There is also a command to
     retire the flashing for the range of SMs associated with the
     page being displayed - 999. This is mainly provided for
     situations such as during installation when SMs are being grown
     and many SMs are displaying recurrent error conditions.

     The backlighted note about the DLIs appears whenever an ONTC is
     out of service or unavailable. The DLIs are under the
     maintenance control of the ONTCs, thus all DLIs on a side are
     affected when the ONTC of that side is off-normal.

     For further details on any SM recovery-related activity or SM
     inhibits, the craft would enter 1800,X to display the SM X
     INHIBIT AND RECOVERY CONTROL page. This is the SMs control page
     for emergency action.

     For details on circuits out of service or hardware in a
     particular SM, the craft would enter 1010,X to display the SM X
     STATUS page. This page can be accessed during the initialization
     of SM X or if SM X is isolated, but the only status that will
     fill in are the SM STAT and RELATED PAGES boxes.

     For details on ONTC circuits out of service, the craft would
     enter 115 to display the COMMUNICATION MODULE SUMMARY page.

     In the example of the 141 page shown in Figure .AW G331/, SM 1, which
     is an LSM, has several off-normal conditions. The ``+''
     indicates that there is more than one off-normal condition.  For
     the most critical condition, inhibits are set. Both SM 3 and 10
     have circuits out of service.  The SM 5, an RSM, has a hash
     error plus other off-normal conditions.  The SM 06, another LSM,
     is isolated. This indicator would be flashing in the display,
     which cannot be shown here.  The SM 48, another RSM, has a
     building power alarm plus other off-normal conditions.  There is
     an off-normal condition in ONTC 1 causing all the DLIs on Side 1
     to be off-normal.

     All available displays can be accessed from the 141 through 144
     display pages.

       CMD     RESULT

       900     The off-normal report is output for the SMs associated
               with the page
               (OP:SYSSTAT,SM=a&&b) [,LSM] [,HSM] [,RSM] [,UCL]
               where a&&b is the range of SMs associated with the page
               being displayed
       999     SM flashing is retired for the range of SMs associated with
               the page
     1010,X    SM X STATUS page is displayed
      1271     SM 1 - 48 REX SUMMARY page is displayed
     1600,SZ   SITE Z STATUS page is displayed
     1800,X    SM X INHIBIT AND RECOVERY CONTROL page is displayed

     The 150 page display provides status information on all
     circuit-switched calls of a particular directory number (DN) or
     multiline hunt group (MLHG) member.
     Effective with the 5E8 software release, the 150 page was
     enhanced to display call ID (CID) information in addition to the
     subaddress (SA) information displayed in earlier software
     releases.  Accordingly, the title of the page was changed from
     SUBADDRESS STATUS to TRACEABLE CALL STATUS.

     A ``SEE PAGE'' indicator in the upper right corner of the 150
     page identifies associated page displays to access for
     additional call trace information.

     Subaddress Displays

     For custom DSLs and standard Electronic Key Telephone service
     (EKTS) DSLs, information is provided on each subaddress of the
     given DN/MLHG.  The SA number corresponds to button location on
     the terminal; it is not the same as call appearance (CA) number,
     but they are related values.  The first CA of a DN/MLHG at the
     terminal is SA 0.  The SA values are then incremented for each
     subsequent appearance of the same DN/MLHG at the terminal.  A
     maximum of 16 SAs can be assigned per DN/MLHG.

     The SA information is shown in four columns on the 150 page and
     includes the following:

       o  SA:  Subaddress number

       o  PDN:  Primary DN of the port controlling the SA

       o  CH:  Channel used

       o  T:  Type of call (V for voice or D for data).

     This information is displayed in response to a DN/MLHG trace
     where SA=ALL was specified, or when an attempt is made to trace
     an invalid (that is, unassigned) SA number.  A valid SA can be
     traced by using the SA option in the trace request.

     The status of SAs is indicated by color: ``ACTIVE'' SAs are
     backlighted in green, ``ON HOLD'' SAs are backlighted in blue,
     and ``IDLE'' SAs are backlighted in white.  Unassigned SAs are
     not backlighted.  At least one SA will appear to be assigned
     even if no voice channels are subscribed to.  If an SA is ON
     HOLD, no B channel will be allocated for the call.  If an SA is
     IDLE, only the SA number will appear.

     Shared analog lines only use SA 0.  Analog controllers are
     marked by an asterisk (*) in the channel information fields.

     If the given DN/MLHG is permitted to make circuit-switched data
     (CSD) calls, this information will also be provided in the 150
     page display. The information provided is the same as for
     circuit-switched voice (CSV) calls with the exception of SA
     information.  Since CSD calls do not use SAs, they are assigned
     a call ID number instead.  This ID number will always be 16.
     Only one CSD call is permitted on these DSLs.  A data call can
     be traced by specifying CID=16 in the input command or poke.

     The SA options are not supported for PODS (ISDN equivalent of
     POTS) lines.

     Figures .AW G332/ and .AW G333/ are examples of the 150 page subaddress
     displays.

     Call ID Display

     For standard non-EKTS DSLs, information is provided based on the
     subscribed-to call reference busy limits (CRBL) for the DN/MLHG.
     The combined value of the CSV CRBL and the CSD CRBL determines
     the number of call positions shown as assigned.  Up to 16 CSV
     calls and 16 CSD calls per DN can be present on standard
     interfaces.

     When the 150 page is populated, each call is given a CID number
     based on the age of the call; the most recent call will be CID
     00, the next will be CID 01, and so on.  This CID number does
     not correspond in any way to button locations on the terminal;
     its only use is to indicate chronological order and to provide a
     means of specifying which of the calls displayed the user wishes
     to trace.

     The CID information is shown in four columns on the 150 page and
     includes the following for each call:

       o  ID:  Identification number

       o  PDN:  Primary DN of the port controlling the call

       o  CH:  Channel used

       o  T:  Type of call (V for voice or D for data).

     Since DNs on non-EKTS cannot be shared, the PDN will be the same
     for each call displayed.

     The status of active calls is indicated by color: ``ACTIVE''
     calls are backlighted in green, ``ON HOLD'' calls are
     backlighted in blue, and ``IDLE'' call positions are backlighted
     in white.  Call positions that exceed the total of the CRBLs are
     not backlighted.  If a call is ON HOLD, no B-channel will be
     allocated for the call.  If a call position is IDLE, only the ID
     number will appear.

     The CID information is displayed on the 150 page by specifying
     CID=ALL in the input command or by attempting to trace an
     invalid CID value.  The call corresponding to a valid CID number
     can be traced by specifying the CID value in the input command.
     If the 150 page is already populated, then the call shown in the
     corresponding ID box will be traced; if not, then the ``Xth''
     oldest call will be traced where X is the CID value specified.

     An example of the CID version of the 150 page display is shown
     in Figure .AW G334/.

     Figure .AW G332/ is an example of the SA version of the 150 page
     display which shows the status of calls on an MLHG.

     Figure .AW G333/ is an example of the SA version of the 150 page
     display which shows the status of calls of a DN.  In this
     example, CSD information is also displayed in the left column
     near the bottom.

     Figure .AW G334/ is an example of the CID version of the 150 page
     display which shows the status of calls for a DN.

     Refer to Page 131 - Call Trace Menu (Figure .AW G319/) and Page 132 -
     Call Trace Menu Cont. (Figure .AW G320/) for the complete list of call
     trace poke commands that can be invoked.  Also, any call trace
     page display can be accessed from the 150 menu page.
     The 151 page display shows the hardware paths to the conference
     circuit when a conference call is traced.
     Conference circuits are located in the Global Digital Service
     Unit (GDSU) and provide 3-port or 6-port customer service
     conferencing capabilities for an office.  The maximum number of
     hardware paths for 3-port and 6-port conference circuits is 3
     and 6 respectively.

     When calls involving more than one conference circuit are
     traced, only the first conference circuit found is displayed.  A
     multiple-conference circuit call is identified by the existence
     of an associate conference controller, or an associate floating
     conference controller, in the TRC UTIL LINE output message on
     the ROP.  To view the connections of the other conference
     circuits on the call, trace the associate conference controllers
     found in the TRC UTIL LINE output message, using the PID option
     on the TRC UTIL input message.

     The NCT time slot numbers have the format ``aaa bbb'' for an
     intramodule path on the conference circuit SM.  For an
     intermodule path between SM ``ddd'' and the conference circuit
     SM, the format is ``ccc SM=ddd''.  The letter ``A'' next to the
     SM number indicates that automatic time slot switching
     (AUTISSING) has occurred.  AUTISSING is a failure with the E-bit
     data on the major side of the TMS.  Therefore, the time slot
     number represented in this situation is from the minor side of
     the TMS.

     All of the dynamic data associated with the traced conference
     circuit can be dumped to the ROP from any call trace page by
     using poke 450 and the PID of the conference circuit process or
     STRUCTS=confckt.

     A ``SEE PAGE'' indicator in the upper right corner of the 151
     page identifies associated page displays to access for
     additional call trace information.

     Figure .AW G335/ shows an example of the 151 page display.  In this
     example, the indicator ``SEE PAGES 133, 134, 135'' directs the
     user to the 133, 134, and 135 pages for more details.

     Refer to Page 131 - Call Trace Menu (Figure .AW G319/) and Page 132 -
     Call Trace Menu Cont. (Figure .AW G320/) for the complete list of call
     trace poke commands that can be invoked.  Also, any call trace
     display page can be accessed from the 151 display page.
     The SM Page Index page provides an index to the SM and remote
     switching module/remote integrated services line unit
     (RSM/RISLU) pages.
     The 1000 page is an index to the primary SM/RSM/RISLU pages that
     directly have status reflected on the 1010 - SM X STATUS page.
     No status is displayed on the 1000 page.

     The page is divided into two parts. The first part displays all
     the pages that are valid for local switching modules (LSM), host
     switching modules (HSM), and RSMs/RISLUs. The second part
     displays the pages that are only valid for RSMs/RISLUs and
     remote sites.

     Some pages shown on the 1000 page reference additional pages
     that provide more detailed information.  These additional pages
     may not appear on the 1000 page.

     Most SM pages are specified using an SM number.  Some pages,
     however, are referenced by the site number of a remote site.
     For these pages (such as the 1600,SZ page), the ``S'' shown on
     the 1000 page is actually entered as part of the menu command.
     For example, entering ``1600,S3'' will display the status of
     RSMs/HSMs at Site 3.

     For all pages, once an SM page has been displayed for a
     particular SM, any other page for that SM may be requested
     without respecifying the SM number.

     The page index shown in Figure .AW G336/ is a listing of the primary
     SM and SITE maintenance displays.  Included in this example are
     the 186Y,X and 187Y,X pages which are new for 5E8.

     All available paging commands can be entered from this display.

 4
     LSM and HSM Pages

      CMD                             RESULT

     1010,X   SM X - STATUS page is displayed
     102Y,X   SM Y - LU X CONCENTRATOR page is displayed, if equipped
     103Y,X   SM X - LU Y SG 0 page is displayed, if equipped
     104Y,X   SM X - LU Y SG 1 page is displayed, if equipped
     105Y,X   SM X - TU Y SG 0 page is displayed, if equipped
     106Y,X   SM X - TU Y SG 1 page is displayed, if equipped
     107Y,X   SM X - DCTU Y page is displayed, if equipped
     108Y,X   SM X - LDSU Y SG 0 AND 1 page is displayed, if equipped
     109Y,X   SM X - RAF Y page is displayed
     110Y,X   SM X - GDSU Y page is displayed, if equipped
     1110,X   SM X - ISTF page is displayed
     112Y,X   SM X - DLTU Y page is displayed, if equipped
     113Y,X   SM X - MSU Y SG 0 page is displayed, if equipped
     114Y,X   SM X - MSU Y SG 1 page is displayed, if equipped
     115Y,X   SM X - DCLU Y page is displayed, if equipped
     1186,X   SM X - PSU NETWORK page is displayed
     1190,X   SM X - MCTSI page is displayed
     1200,X   SM X - DLI/TMSLNK page is displayed
     1280,X   SM X - REX STATUS page is displayed
     1460,X   SM X - DATA LINK DSLS page is displayed
     170Y,X   SM X - ISLU Y NETWORK page is displayed
     1800,X   SM X - INHIBIT AND RECOVERY CONTROL page is displayed
     186Y,X   SM X - IDCU Y Circuit page is displayed, if equipped
     187Y,X   SM X - IDCU Y Facility page is displayed, if equipped
     1900,X   SM X - CLNKS page is displayed

 4
     RSM/RISLU PAGES

       CMD                                 RESULT

     1160,X    SM X - MISC UNITS page is displayed, if equipped
     1170,X    SM X - RCLK page is displayed, if equipped
     1190,X    SM X - MCTSI/RLI page is displayed
     1400,X    SM X - RSM BLDG/PWR ALARMS page is displayed, if equipped
     1420,SZ   RISLU BLDG/PWR page is displayed
     145Y,X    RISLU DLTU Y page is displayed
     1600,X    SM X - SITE STATUS page is displayed via SM number, if equipped
     1600,SZ   RSM/RISLU SITE STATUS page is displayed
      1610     RSM SITE INDEX page is displayed
      1615     ORM SITE INDEX page is displayed
     1620,SZ   RISLU SITE STATUS page is displayed
      1630     RISLU SITE INDEX page is displayed
     170Y,X    RISLU Y NETWORK page is displayed

     The purpose of the 186Y,X display page is to show the status of
     service groups (SG) for an Integrated Digital Carrier Unit
     (IDCU).
     Each IDCU has two SGs, both of which are shown on the 186Y,X
     display page.  Each SG has a common board (IDCU COM) and up to a
     maximum of two loop side interfaces (LSI).  The IDCU COM
     actually consists of two boards:  a common control processor
     (CCP) board and a PIDB time slot interchanger (PTI) board.  An
     IDCU also can have up to two electrical line interfaces (ELI).
     The LSIs and ELIs will be shown on the 186Y,X display page only
     if their circuits exist.

     The status of LSIs will be the same as that of the host SG
     unless the LSIs are in growth or unequipped, in which case they
     have their own status and will display GROW or UNEQ as
     appropriate (see Figure .AW G337/).  The status of ELIs will always be
     displayed.

     Information on IDCU facilities and IDCU remote terminals is not
     displayed on the 186Y,X page.  When the text string SEE PAGE
     187Y FOR IDCU Y FAC INFO is backlighted (see Figure .AW G338/), there
     are off-normal conditions with either the IDCU facilities and/or
     the IDCU remote terminals.  A user would then go to Page 187Y,X
     for additional information about the trouble.

     Figure .AW G337/ is an example of the 186Y,X page equipped with three
     LSIs and one ELI.  The status shown for two of the LSIs is GROW
     and UNEQ.  The third shows no text status which means that its
     status is ACT (same as SG 0).

     Figure .AW G338/ is an example of the 186Y,X page equipped with two
     ELIs.  No text status is shown for any of the LSIs which means
     their status is the same as that of their respective SGs.  The
     text string SEE PAGE 187Y FOR IDCU Y FAC INFO is backlighted
     indicating trouble with the IDCU facilities and/or the IDCU
     remote terminal.

     Commands on the 186Y,X page allow a user to remove, restore,
     diagnose, and switch IDCU service groups and to remove and
     restore ELIs.

 2
     CMD                             RESULT

     20X   IDCU service group X is removed.
           (RMV:IDCU=SM#-IDCU#-X)[,UCL]
     21X   ELI X is removed.
           (RMV:IDCUELI=SM#-IDCU#-X)[,UCL]
     30X   IDCU service group X is restored.
           (RST:IDCU=SM#-IDCU#-X)[,UCL]
     31X   ELI X is restored.
           (RST:IDCUELI=SM#-IDCU#-X)
     400   IDCU service group is switched.
           (SW:IDCU=SM#-IDCU#)
     50X   IDCU X is diagnosed.
           (DGN:IDCU=SM#-IDCU#-X,RAW,TLP)[,UCL]
           [,RPT] Test will be repeated 32,767 times.
           [,RPT=a] The ``a'' represents the number of times the test
           is to be repeated (1-32,767).
           [,PH=b|b&&c] The ``b'' represents the diagnostic phase or
           ``b&&c'' is the range of diagnostic phases.

     The purpose of the 187Y,X display page is to show the status and
     far-end connections of Integrated Digital Carrier Unit (IDCU)
     facility circuits (IFAC).
     Each IDCU can have up to 40 (maximum) IFACs.  Information on the
     IFACs is shown in table format on the 187Y,X display page.  Four
     3-column tables are used; each table displays information for up
     to 10 IFACs.

     An IFAC may or may not terminate on a remote terminal (RT).  If
     it terminates on an RT, the RT number is shown in the RT column
     of the status table.  If it does not terminate on an RT, NR (Not
     To RT) appears in the RT column.  An ampersand (&) beside the RT
     number means the facility is a protection line; an asterisk (*)
     means the facility has the Embedded Operation Channel/Time Slot
     Management Channel (EOC/TMC).  Red backlighting of the RT number
     indicates an off-normal condition in the RT.  For additional
     information on the off-normal RT, the user should go to the
     188YZZ,X page (Y=IDCU #, ZZ=RT #, and X=SM #).  For example,
     with the screen display shown in Figure .AW G339/, the user would go
     to Pages 188511 and 188503 for off-normal conditions of RT 11
     and RT 3 respectively.

     The IFACs on protection (meaning traffic of the facility is
     going through the protection line) will be shown as being in
     either the PROT or FELP state.  The reason for an IFAC being on
     protection can be determined by distinctive display colors as
     explained in Table .AW TAO/.

     When an IFAC has an alarm, the alarm will be indicated in the
     alarm column (ALM) of the status table.  Possible alarms are as
     follows:

     Carrier Group Alarms (CGA):

       o  CA:  CGA Alarm Indication Signal (AIS)

       o  CL:  CGA Local

       o  CR:  CGA Remote.

     Carrier Failure Alarm (CFA):

       o  A:  AIS CFA

       o  B:  Bit Error Rate

       o  L:  Local CFA

       o  R:  Remote CFA.

     Figure .AW G339/ is an example of the 187Y,X display page.

     Commands on the 187Y,X page allow a user to remove and restore
     IFACs.

     CMD              RESULT

     2XX   IFAC XX is removed.
           (RMV:IFAC=SM#-IDCU#-XX)[,UCL]
     3XX   IFAC XX is restored.
           (RST:IFAC=SM#-IDCU#-XX)

     The purpose of the 188YZZ,X display page is to show the remote
     terminal (RT) circuit status and facility connections for an
     Integrated Digital Carrier Unit (IDCU).
     The 188YZZ,X page has two versions:  the TR008 RT and the TR303
     RT.  Only one version can be displayed at a time.

     TR008 RT Version

     The TR008 RT version of the 188YZZ,X page shows the site
     identification (SID) number, facility connections, digroups, and
     alarm for the RT.

     The TR008 RT can be Mode I, Mode II, or a combination of the two
     modes.  Mode I (Figure .AW G340/) is equipped with digroups.  Mode II
     (Figure .AW G341/) is equipped with dual digroups.  A combination of
     Mode I and Mode II (Figure .AW G342/) has both digroups and dual
     digroups.  A facility can terminate on either of the three
     configurations.  The 188YZZ,X display page shows facilities from
     two points of view:  IDCU (IFAC) and RT (RTFAC).  Although the
     two views are shown in separate boxes, they are physically the
     same entity.

     The TR008 RT can have one protection line facility.  The
     protection line facility is shown on the display as RTFAC P.
     When the protection line is in use by a facility, the REPLACES
     box will backlight white, and the name of the facility on
     protection will be displayed in the box beneath the RTFAC P
     indicator.  The status of the RTFAC on protection will be shown
     as either PROT or FELP.

     The TR008 RT is equipped with a power/miscellaneous (PWR/MISC)
     alarm which shows major or minor alarm conditions.

     TR303 RT Version

     The TR303 RT version of the 188YZZ,X page shows the SID number,
     the RTFACs and associated IFACs, Embedded Operations
     Channels/Time Slot Management Channels (EOC/TMC) facilities,
     protection facility, and alarms for the RT.

     Information for each of the 28 RTFACs (maximum) that can
     terminate on the TR303 RT is shown in table format in the center
     of the page. An ampersand (&) in the table beside the RTFAC
     number means the facility is a protection line; an asterisk (*)
     means the facility has the EOC/TMC.

     Information on the protection facility is shown on the right
     center of the page under the EOC/TMC indicator.  The TR303 RT
     can have one protection line facility.  When the protection line
     is in use by a facility,  the facility number of the protection
     line and the facility it replaces will be shown.  The status of
     the RTFAC on protection will be shown as either PROT or FELP.

     The TR303 RT has 2 EOCs and 2 TMCs.  The first facility, RTFAC
     1, always has one EOC/TMC.  The EOC/TMC circuits and their
     status are shown at the top right of the page display.

     The TR303 RT can display the following six alarms:

       o  PWR:  Power

       o  ENV1:  Environmental 1

       o  ENV2:  Environmental 2

       o  CRIT:  Critical

       o  MAJ:  Major

       o  MIN:  Minor.

     The text string SEE PAGE 187Y FOR IDCU Y FAC INFO is used in
     both versions to inform the craft to go to the IDCU Facility
     page for facility information.

     An example of the TR303 RT version is shown in Figure .AW G343/.

     Figure .AW G340/ is an example of the TR008 RT version in Mode I, the
     digroup configuration mode.  In this example, RTFAC B is on
     protection as indicated by its PROT status and its being named
     with REPLACES in the box beneath the protection line facility
     (RTFAC P).

     Figure .AW G341/ is an example of the TR008 RT version in Mode II, the
     dual digroup configuration mode.  In this example, RTFAC AB is
     on protection and IFAC 12 is the protection line.

     Figure .AW G342/ is an example of the TR008 RT version in a
     combination Mode I and Mode II configuration.  In this example,
     RT 13 does not have a protection line.

     Figure .AW G343/ is an example of the TR303 RT version of the 188YZZ,X
     page.  In this example, RTFAC 05 is a protection line facility
     that replaces RTFAC 01 which is in FELP.

       Note:   A facility is on protection when it is FELP.

     The RTFACs 01 and 03 have the EOC/TMC facilities.  Alarms ENV1
     and ENV2 are displayed.

     Commands on the 188YZZ,X page allow a user to remove and restore
     IFACs, EOCs, and TMCs, to switch EOCs and TMCs, and to output
     TEI status.

 2
     CMD                    RESULT

     2XX   IFAC XX is removed.
           (RMV:IFAC=SM#-IDCU#-XX,SCREEN=RT#)[,UCL]
     24X   EOC X is removed.
           (RMV:EOC=SM#-IDCU#-RT#-X)[,UCL]
     25X   TMC X is removed.
           (RMV:TMC=SM#-IDCU#-RT#-X)[,UCL]
     3XX   IFAC XX is restored.
           (RST:IFAC=SM#-IDCU#-XX,SCREEN=RT#)
     34X   EOC X is restored.
           (RST:EOC=SM#-IDCU#-RT#-X)
     345   TMC X is restored.
           (RST:TMC=SM#-IDCU#-RT#-X)
     400   EOC is switched.
           (SW:EOC=SM#-IDCU#-RT#)
     401   TMC is switched.
           (SW:TMC=SM#-IDCU#-RT#)
     900   TEI status is output.
           (OP:RT,CHAN,LRT=SM#-IDCU#-RT#)

     This subsection contains descriptions and examples of the master
     control center (MCC) page displays that were added with or
     changed with the 5E9(1) software release.

     Refer to Table .AW TAF/ for a complete listing of MCC page displays.
     The purpose of the 100 page index is to provide an index of main
     system pages.
     This index is a listing of primary maintenance displays and is
     also an entry point into other subsystem displays, such as trunk
     and line maintenance, equipment configuration data (ECD), and
     office dependent data recent change and verify (ODD RC/V).

     The per-switching module (SM) pages are not shown on this
     display.  The SMs have their own index (1000 - SM PAGE INDEX).

     There is a direct correlation between the page numbers of Pages
     105 through 116 (except 108) and the physical position of the
     status summary indicators in the SUMMARY STATUS AREA.  For
     example, the fifth status summary indicator in the SUMMARY
     STATUS AREA (from left to right) is BLDG/PWR.  Its associated
     display is 105 - BLDG/PWR & ALARM CONTROLS.  Some of the status
     summary indicators do not have an associated display page.
     These are listed on the index as ``NOT ASSIGNED.''  This is a
     built-in trouble-locating shortcut.  The page number for an
     alarm can be derived from the alarmed indicator's position
     without going to this display, although this display is always
     available.

     Information on ODD can be found in AT&T 235-600-105,
     Translations Data Manual.  Also, all RC/V views are described in
     AT&T 235-118-2XX (XX = manual number associated to the
     applicable software release), Recent Change Procedural Manuals.
     Refer to AT&T 235-000-000, Numerical Index - Division 235 and
     Associated Documents, for the complete list of RC/V manuals.

     Information on equipment configuration data/system generation
     (ECD/SG) RC/V can be found in AT&T 235-600-30X (X = manual
     number associated to the applicable software release), ECD/SG
     Data Base Manual.  Refer to AT&T 235-000-000, Numerical Index -
     Division 235 and Associated Documents, for the complete list of
     ECD/SG manuals.

     Pages 196, 198, and 199 (RC/V pages) do not appear when the 100
     Page Index page is displayed at the switching control center
     (SCC) because the RC/V pages cannot be displayed at that
     location.

     Page 118 (CNI RING STATUS) is shown depending on switch
     configuration.

     Effective with the 5E9(1) software release, some pages appearing
     in the 100 page index are assigned a command group which is used
     to control access to the pages.  This is part of ``authority
     management'' which is described in detail in AT&T 235-105-210,
     Routine Operations and Maintenance Procedures.  The command
     group name for affected pages is shown in Section .RM 4.6.2.3/,
     following.

     Figure .AW G344/ shows an example of the 100 page index.

     The commands on this page can be entered from any display page,
     under normal operation. Also, any available per-SM display can
     be accessed. See 1000 - SM PAGE INDEX (Figure .AW G336/) for details.

     The command group name, if applicable, is shown in parentheses
     at the end of the description (RESULT) of each command.  Command
     group descriptions can be found in AT&T 235 600-700, Input
     Messages Manual, Command Group Appendix.
 2

       CMD     RESULT

       100     PAGE INDEX is displayed
     105/106   BUILDING/POWER AND ALARM CONTROLS page is displayed
       107     CIRCUIT LIMIT page is displayed
       109     OVERLOAD page is displayed
       110     SYSTEM INHIBITS page is displayed
     111/112   AM, AM PERIPHERALS page is displayed
       113     OPERATIONS SYSTEMS LINKS page is displayed
       114     EQUIPPED SM STATUS SUMMARY page is displayed
       115     COMMUNICATION MODULE SUMMARY page is displayed
       116     MISCELLANEOUS page is displayed
       117     IOP APPLICATION PROCESSOR DATA LINKS page is displayed
       118     CNI RING STATUS page is displayed
       119     MISCELLANEOUS ALARMS page is displayed
       120     MESSAGES page is displayed
       121     IOP 0 & 1 page is displayed
       122     IOP 2 & 3 page is displayed
       123     DFC 0 & 1 STATUS page is displayed
       124     SOFTWARE RELEASE RETROFIT page is displayed
       125     DFC 2 & 3 STATUS page is displayed
       126     DFC 0 & 1 PERFORMANCE page is displayed
       127     MTIB page is displayed
       128     DFC 2 & 3 PERFORMANCE page is displayed
       129     DEFENSE SERVICES NETWORK NM EXCEPTION page is displayed
       130     NM EXCEPTION page is displayed
       131     CALL TRACE MENU page is displayed
       160     TRUNK AND LINE MAINTENANCE INDEX is displayed
       178     AUTO SPARE DISK page is displayed
       179     DISK CONFIGURATION page is displayed
       180     DISK CONFIGURATION page is displayed
       181     OFFLINE SM 1-48 STATUS SUMMARY page is displayed
       182     OFFLINE SM 49-96 STATUS SUMMARY page is displayed
       183     OFFLINE SM 97-144 STATUS SUMMARY page is displayed
       184     OFFLINE SM 145-192 STATUS SUMMARY page is displayed
       190     C/D UPDATE page is displayed
       191     OS STATUS page is displayed
       193     VERIFY TEXT page is displayed (FHADM)
       194     SCREEN page is displayed (SPECRCV)
       195     GENBACKUP page is displayed (FHADM)
       196     ODD RC/V is started. NOT FOR USE FROM SCC (RCV)
       197     CUTOVER page is displayed
       198     SG RC/V is started. NOT FOR USE FROM SCC (SPECRCV)
       199     ECD RC/V is started. NOT FOR USE FROM SCC (SPECRCV)
      1000     SM PAGE INDEX page is displayed
      1209     ONTC 0 & 1 page is displayed
      1210     MI/NC 0 & 1 page is displayed
      1220     TMS 0 & 1 SUMMARY page is displayed
      1240     MSGS 0 SUMMARY page is displayed
      1250     MSGS 1 SUMMARY page is displayed
      1260     CLNK SUMMARY page is displayed
      1271     REX STATUS page is displayed
      1850     CMP INHIBIT AND RECOVERY CONTROL page is displayed
      1940     EASY BWM INSTALLATION page is displayed
      1941     BWM AUTOMATION SCHEDULING page is displayed
      1950     PROGRAM UPDATE MAINTENANCE MENU page is displayed
      1960     BWM INSTALLATION page is displayed
      1999     STATE DEFINITIONS page is displayed


     The 107 display page provides a listing of trunk groups that
     have reached or exceeded their automatic maintenance limit
     (AML).  The AML for each trunk group is set through Recent
     Change View 5.1.  Effective with the 5E9(1) software release,
     the 107 page shows the PRI D-channel status.
     Two counts are maintained by the 5ESS(R) switch for each trunk
     group in an office.  These counts are as follows:

       o  TG OOS:  Total number of out-of-service (OOS) members
          (individual trunks)

       o  AML OOS:  Total number of OOS members (individual trunks)
          having OOS status due to AML reasons.

     If a trunk group's AML OOS count has reached its automatic
     maintenance limit, its TG OOS count has also reached its
     automatic maintenance limit, but not vice versa.

     When a trunk group's AML is reached or exceeded by either count,
     the trunk group number will be shown on the display.  In the
     SUMMARY STATUS AREA, the CKT LIM indicator will be backlighted
     and flashing. The associated alarm level (CRITICAL, MAJOR, or
     MINOR) will also be backlighted, as applicable.

     The 107 page display lists in numerical order the number(s) of
     the first 40 trunk groups that have reached or exceeded their
     AML.  When more than 40 trunk groups have reached or exceeded
     their AML, the word ``EXCESSIVE'' will be backlighted at the
     bottom of the listing.  No trunk group numbers are shown on the
     page display if all trunk groups are normal.

       Note:   A trunk group with its AML set to 0 will not be
               included on the page display until this limit is
               actually exceeded (that is, at least one member has
               to be OOS for a trunk group to be included on the
               display).

     In 5E9(1), poke 902 and the status box for primary rate
     interface (PRI) groups were added to the 107 page.  The PRI
     STATUS box is pertinent only if the office is equipped with
     PRIs.  If the office has no PRIs, the PRI STATUS box will always
     indicate not applicable (NA) (see Figure .AW G345/).  If the office
     has PRIs provisioned and all D-channels are in service (IS), the
     PRI STATUS box shows NORMAL.  If any of the equipped PRI D-
     channels are OOS for any reason, the PRI STATUS box shows DCH
     OOS and is backlighted (white on red), and the CKT LIM indicator
     is backlighted and flashing.

     The DCH OOS indicator is caused either by fault recovery actions
     of the switch or by craft action (RMV:TRK command).  If it is
     caused by fault recovery, the associated alarm level (CRITICAL
     or MAJOR) will backlight.  If it is caused by craft using the
     RMV:TRK command, there will be NO associated alarms.

     Figure .AW G345/ is an example of the 107 display page for an office
     not equipped with PRIs.  In this example, an excessive amount of
     trunk groups (more than 40) are OOS as reflected by the
     backlighted indicator ``EXCESSIVE''.  The PRI STATUS box shows
     NA which indicates that the office has no PRIs.  A MAJOR alarm
     condition is shown, and CKT LIM is backlighted.

     Figure .AW G346/ is an example of the 107 display page for an office
     equipped with PRIs.  In this example, an excessive amount of
     trunk groups (more than 40) are OOS as reflected by the
     backlighted indicator ``EXCESSIVE''.  The PRI STATUS box shows
     DCH OOS indicating that at least one PRI has lost a D-channel.
     A CRITICAL alarm condition is shown, and CKT LIM is backlighted.

     Commands are provided to output listings of all trunk groups
     whose AML OOS count has reached or exceeded their respective
     AMLs, those having an OOS member(s), and those having an off-
     normal PRI D-channel.

     All available paging commands can be entered from the 107 page.

     CMD   RESULT

     900   Listing of trunk groups whose AML OOS count has reached or
           exceeded their respective AMLs is printed at the ROP
           (OP:AML[,TG=a])
           where ``a'' is a specific trunk group number.
     901   Listing of trunk groups having any OOS member(s) is printed at
           the ROP (OP:TGCNT[,TG=a]) where ``a'' is a specific trunk group
           number.
     902   Listing of trunk groups having any off-normal condition on a PRI
           D-channel is printed at the ROP (OP:OFFNORM,PRIGRP).

     The 109 display page provides an indication of resource or
     real-time overloads in the AM, SM(s), CMP, and direct link nodes
     (DLN) (if equipped) and commands to inhibit or allow essential
     service protection (ESP).
     Any AM, SM, CMP, or DLN overload conditions are shown on the 109
     display page.  If an SM overload occurs, the SM number and type
     will be displayed in the indicator and backlighted. If more than
     16 SMs are in overload, a note will appear, partially
     backlighted, indicating how many SMs are overloaded.  For a
     complete list of SMs in overload, enter the 900 command.  If a
     CMP overload occurs, the CMP number and whether it is the
     primary (P) or mate (M) are shown.  If a DLN overload occurs,
     the DLN number is shown.

     Details on any of the overloads are shown on display page 170.

     The REALTIME overload indicators will contain NONE, MINOR,
     MAJOR, or CRIT to show the severity of the overload. NONE means
     no overload exists. MINOR and MAJOR are different levels of
     real-time overloads.

     The only craft action which can be taken during overload
     conditions is to reduce or eliminate input messages/maintenance
     commands.  All other actions are initiated by the system.

     For AM RESOURCE overloads, either NONE or the name of the
     resource will be displayed. The monitored resources are as
     follows:

       o  MCB - Message Control Block

       o  PCB - Process Control Block

       o  SCB - Stack Control Block

       o  TCB - Timer Control Block

       o  MSG - Message Overflow (because of PIC overload).

     Resources for the SMs, CMP, and DLN are shown on the 170 display
     page.

     When Essential Service Protection (ESP) is allowed, it gives
     preferential treatment to designated lines (for example,
     hospitals, police, fire departments, etc.) during periods of
     overload.  The normal mode of ESP is set to either YES or NO by
     each office on RC/V view 8.1 (ESP NORM ALW).  If ESP NORM ALW is
     set to YES, the INHIBITED text is backlighted when inhibited.
     If ESP NORM ALW is set to NO, The ALLOWED text is backlighted
     when allowed.

     If the network management control is on to prevent overloads in
     this office, the ``SEE PAGE 130'' indicator will appear and be
     backlighted.

     An overload will cause the OVERLOAD indicator at the top of the
     screen to backlight. The associated alarm level (CRITICAL,
     MAJOR, or MINOR) will also backlight, if applicable.  An
     overload will also cause the ``SEE PAGE 170 FOR MORE OVERLOAD
     INFO'' indicator in the upper right portion of the 109 page to
     backlight.

     The AM information box contains information regarding real-time
     and resource overloads in the AM.

     The SM information provided on Page 109 is limited; the SM
     number and type.  For additional information on a specific SM,
     see Page 170.

     As with the SM, the 109 page provides limited information on the
     CMP.  If a CMP is in OVERLOAD, information shown is the CMP
     number and whether the CMP is the primary or mate.  Additional
     CMP information is available on Page 170.

     The 109 page also displays limited DLN information.  If the DLN
     is in overload, the DLN group and member numbers are shown.

       Note:   The DLN information box is displayed only if the
               office is equipped with a DLN.

     Figure .AW G347/ shows an example of the 109 display page with
     specific AM overload information. It also shows up to 16 of the
     SMs and up to 8 of the CMPs that are in overload.  The note
     EXCESSIVE is displayed and backlighted because there are greater
     than 16 SMs in overload. The actual number of SMs in overload
     (20) is displayed.  The example also shows the DLN00-2 and
     primary CMP00 are in overload.

     Commands are provided to inhibit and allow ESP and to output a
     list of all SMs that are overloaded.

     In addition to these commands, any available paging command can
     be entered from Page 109.

     CMD   RESULT

     600   Essential Service Protection is inhibited (INH:ESP)
     700   Essential Service Protection is allowed (ALW:ESP)
     900   Output list of SMs in overload on the ROP (OP:OVRLD:ALL)

     The purpose of the 111/112 display page is to report status of
     the AM and its peripherals.  In 5E9(1) and later software
     releases, an indicator shows if an AM off-line boot is in
     progress.
     The AM is an AT&T 3B20 duplex computer. In addition to the AM
     and peripheral indicators on this display, there are additional
     indicators for Page 121 - IOP 0 & 1, Page 122 - IOP 2 & 3, Page
     123 - DFC 0 - 1 STATUS, Page 125 - DFC 2 & 3 STATUS, and Page
     113 - OPERATIONS SYSTEMS LINKS. If common network interface
     (CNI) is equipped, there is also an indicator pointing to Page
     118 - CNI RING STATUS.

     An off-normal condition on this page will cause the AM or AM
     PERPH indicator at the top of the screen to backlight. An off-
     normal condition in an MHD (Page 123) will backlight the ``SEE
     PAGE 123'' indicator and the AM PERPH at the top of the screen.
     Also, an off-normal condition in an MHD (Page 125) will
     backlight the ``SEE PAGE 125'' indicator and the AM PERPH at the
     top of the screen.  An off-normal condition on Page 121 will
     backlight the ``SEE PAGE 121'' indicator(s) and the AM PERPH at
     the top of the screen. An off-normal condition on Page 122 will
     backlight the ``SEE PAGE 122'' indicator(s) and the AM PERPH at
     the top of the screen. An off-normal condition on Page 118 will
     backlight the ``SEE PAGE 118'' indicator and the AM PERPH at the
     top of the screen if CNI is equipped. An off-normal condition in
     the SCCs will cause the ``TO SCC 0'' or ``TO SCC 1'' indicator
     to backlight, and the OS LINKS indicator at the top of the
     screen will backlight. In all these cases, the appropriate alarm
     level (CRITICAL, MAJOR, or MINOR) will also backlight, if
     applicable.

     Effective with the 5E9(1) software release, the ``OFLBOOT IP''
     indicator will appear and be backlighted when the AM off-line
     boot is in progress.  If this TTY is associated  with the on-
     line side of the OFLBOOT procedure, the word ``ONLINE'' will
     appear after the indicator.  Conversely, if this TTY is
     associated  with the off-line side, the word ``OFFLINE'' will
     appear.

     Figure .AW G348/ is an example of the regular version of the 111/112
     page with various off-normal conditions in the AM and its
     peripherals.  No off-line boot is in progress in this example.

     The CSU 1 and AM 1 are unavailable. This caused the AM indicator
     at the top of the screen to backlight. An MHD on Page 123 is out
     of service, causing the SEE PAGE 123 to backlight, and there is
     a problem on Page 121 with some device or devices connected to
     IOP controller 0. These two conditions have caused the AM PERPH
     indicator at the top of the screen to backlight. Also, SCC 1 is
     either out of service, unavailable, or being initialized, which
     is shown by backlighting in the TO SCC 1 indicator at the bottom
     right-hand portion of the display. This off-normal SCC condition
     caused the OS LINKS indicator at the top of the screen to
     backlight.

     Figure .AW G349/ is an example of the off-line boot version of the
     111/112 page with abnormal conditions in the AM and its
     peripherals.

     The 111/112 page provides commands to remove, restore, diagnose,
     and switch the various units. Also, output commands are
     available for out-of-service and diagnostic listings.

     All available displays can be accessed from the 111/112 page.
 2

     CMD   RESULT                        CMD   RESULT

     20X   AM X is removed               30X   AM X is restored
           (RMV:CU=X)                          (RST:CU=X)[,UCL]
     21X   DFC X is removed              31X   DFC X is restored
           (RMV:DFC=X)                         (RST:DFC=X)[,UCL]
     23X   IOP X is removed              33X   IOP X is restored
           (RMV:IOP=X)                         (RST:IOP=X)[,UCL]
     24X   MTTYC X is removed            34X   MTTYC X is restored
           (RMV:MTTYC=X)                       (RST:MTTYC=X)[,UCL]
     25X   MTTY X is removed             35X   MTTY X is restored
           (RMV:MTTY=X)                        (RST:MTTY=X)[,UCL]
     26X   ROP X is removed              36X   ROP X is restored
           (RMV:ROP=X)                         (RST:ROP=X)[,UCL]
     50X   AM X is diagnosed             400   AM is switched
           (DGN:CU=X)[,UCL]                    (SW:CU)
     51X   DFC X is diagnosed            401   PORTSW is switched
           (DGN:DFC=X)[,UCL][,CONT]            (SW:PORTSW)
     53X   IOP X is diagnosed            402   ROP is switched
           (DGN:IOP=X)[,CONT][,UCL]            (SW:PORTSW:ROP)
     54X   MTTYC X is diagnosed          403   MTTY is switched
           (DGN:MTTYC=X)[,UCL][,CONT]          (SW:PORTSW:MTTY)
     404   OOS units are listed at ROP
           (OP:CFGSTAT,OOS)
     405   Diagnostic request queue is
           output at ROP, including
           restore/remove requests
           (OP:DMQ,AM)


     The 116 display page provides status for various
     units/activities which do not fall under any other grouping.
     The External Sanity Monitor (ESM) has indicators for alarm,
     inhibit, and power. If an alarm or an inhibit is present, the
     appropriate indicator will backlight. If power is off, the POWER
     indicator will backlight and the word OFF will be displayed.

     The CALL MONITOR indicator shows whether the Call Monitor is
     inhibited or allowed.  Entering the command 601 generates the
     message INH:CALLMON which will inhibit the monitor from making
     test calls and performing call completion analysis.  This also
     clears the monitor's history data.  The command 701 generates
     the message ALW:CALLMON which allows the monitor to start the
     cycle of making test calls and performing call completion
     analysis.  Command 801 generates the message RTR:CALLMON,ALARM
     which retires the alarm indicator in the Call Monitor box.
     Command 901 generates the message OP:CALLMON which generates the
     OP CALLMON PAST 15 MINUTE REPORT on the ROP.

     The indicators FRAME FUSE and FRAME FAN are for the
     miscellaneous frame.  If a fuse or fan alarm is present on the
     miscellaneous frame, the corresponding indicator will backlight.
     The fuse must be replaced to correct the frame fuse alarm.  The
     fan must be restored to operating condition to correct the frame
     fan alarm.  The input command CLR:FANALM,MFFAN can be entered to
     clear the frame fan alarm after the alarm condition is fixed.
     If a system inhibit is present, the word INH will be displayed
     and backlighted to the right of the indicator label.  The fuse
     and fan alarms can only be inhibited by the system.  An inhibit
     means a scan point is chattering.  The input command
     ALW:ALM,MFFAN can be entered to allow the scan point after the
     chattering problem is fixed.

     The indicator GENERIC RETROFIT will backlight and change to
     GENERIC RETROFIT ACTIVE when software release (generic) retrofit
     is in progress.

     The indicator ODD EVOL will backlight and change to ODD EVOL ACT
     when ODD Evolution is in progress. ODD Evolution is initiated by
     the command BKUP:ODD,ODDEVOL and stays in effect until the
     actual software release cutover takes place.

     The indicator OSPS EVOL will backlight and change to OSPS EVOL
     ACT when OSPS Evolution is in progress.  The OSPS Evolution is
     initiated by the command BKUP:ODD,ODDEVOL if the office has an
     OSPS configuration active.  It stays in effect until the actual
     software release cutover takes place.

     The indicator ODD WARNING will backlight when either the amount
     of ODD space being used has exceeded the engineering
     recommendations for the AM or the automatic relation engineering
     reorganization process has failed on one or more relations in
     the AM.  Entering the command 902 generates the input message
     OP:ODDWARN,AM which will generate the OP ODDWARN output message
     on the ROP.

     The RC BACKUP indicator normally shows NORMAL on the right part
     of the indicator. If RC Backup fails in the AM, the text NORMAL
     changes to FAILURE and the entire indicator backlights.

     The MISCELLANEOUS ALARMS indicator has two subindicators: ALARM
     and INHIBIT.  These subindicators are backlighted for any alarm
     and/or inhibit conditions present on the MISCELLANEOUS ALARMS
     display.  For additional information, enter command 119.

     The next indicator, MTIB, will backlight if an off-normal
     condition exists on the MTIB display. Enter command 127 for
     further details.

     In the CUTOVER indicator, the word ACTIVE will backlight if an
     off-normal condition exists on the CUTOVER display (cutover
     enabled, for example). Further information can be found on
     display 197 - CUTOVER.

     The indicator BWM AUTOMATION will backlight when the BWM
     automation process is halted for any reason.

     The indicator SM/CMP FILE shows NORMAL (in the right portion of
     the indicator) while the system is operating normally.  If the
     UPD:HSCHK audit finds hashsum errors on any of the SM/SM
     peripheral/CMP text images, the indicator will backlight and
     NORMAL changes to HASHERR.  For more information, analyze the
     last output message from the UPD:HSCHK command (on the ROP) or
     request a summary report of the errors via the UPD:HSCHK,REPT
     option of the command.  The indicator is cleared when the cause
     if the disk hashsum error has been corrected and the UPD:HSCHK
     audit is re-run.

     Any off-normal condition will cause the MISC indicator in the
     SUMMARY STATUS AREA at the top of the screen to backlight.

     Figure .AW G350/ is an example of the 116 display page which shows an
     alarm and an inhibit present on 119 - MISCELLANEOUS ALARMS.
     Also, something is off-normal on Page 127 - MTIB STATUS and Page
     1941 - BWM Automation.  There are hashsum errors on the SM or
     CMP.  These conditions have caused the MISC status summary
     indicator at the top of the screen to backlight.

     Commands are provided to inhibit and allow the ESM and to clear
     (retire) the exit pilot lamps.  Commands are also provided to
     inhibit and allow the call monitor, output the past 15-minute
     interval history for the call monitor, and retire a call monitor
     alarm.

     Also, all available displays can be accessed from the 116
     display page.

     CMD   RESULT

     600   External Sanity Monitor is inhibited (INH:ALM,ESM)
     601   Call Monitor is inhibited (INH:CALLMON)
     700   External Sanity Monitor is allowed (ALW:ALM,ESM)
     701   Call Monitor is allowed (ALW:CALLMON)
     800   Exit Pilot Lamps are cleared (retired) (CLR:LAMPS)
     801   Call Monitor alarm is retired (RTR:CALLMON,ALARM)
     901   Call Monitor history is output (OP:CALLMON)
     902   ODD WARNING information is output (OP:ODDWARN,AM)

     The purpose of the 118 page is to give the status of the 5ESS
     switch CNI hardware and CCS signaling links by providing
     information on the individual ring nodes and signaling link
     states.
     The 118 page is divided into five basic areas: upper left, upper
     center, upper right, lower left, and lower right.  The upper
     left area (RING STAT) shows the CNI ring status and automatic
     ring recovery (ARR) information.  The upper center area (STATUS)
     shows office signaling status.  The upper right area (ALARMS)
     shows the fan and fuse alarm status for CNI hardware.  The lower
     left area (GRP/MEM) shows the status of each CNI group with its
     associated ring nodes and signaling links.  The lower right area
     shows a listing of up to 10 INACCESSIBLE POINT CODES.

     Following are descriptions of the upper left area indicators:

     RING STAT Indicator

     The purpose of this indicator is to show the state of the CNI
     ring.  Following is a list of the possible states and their
     meanings:

       o  ACTIVE:  The CNI ring has all nodes active.

       o  DOWN:  The CNI ring has a critical problem; CCS call
          processing cannot be completed.

       o  ISOLATED SEGMENT:  The ring has one or more nodes under
          diagnostics which requires a quarantine or isolation of the
          node.

       o  RESTORING:  The node is being pumped and should go ACTIVE
          soon.

       o  CONFIGURING:  The ring has just RESTORED a node and is
          propagating the token to allow the node back into service
          with the rest of the ring.

     ARR Indicators

     The ARR indicators are not seen on the 118 page until a node is
     faulted.  Once a node is down and ARR attempts to recover the
     node, the appropriate indicator will display and light.  The ARR
     has three indicators which appear at the upper left corner of
     the 118 page just under RING STAT.  The ARR indicators show the
     type of recovery being done and the group/member number of the
     node currently being worked on.  If more than one node is down,
     an OP:DMQ may be performed at the bottom of the MCC to see if
     the node has been queued for restoral by ARR.

     Critical Node Recovery (CNR) is a higher automatic level of node
     recovery than ARR.  The CNR is invoked when there is a duplex
     failure of CCS link nodes.  Automatic Critical Node Recovery
     (ACNR) is also a higher automatic level of node recovery than
     ARR.  The ACNR is invoked when there is a duplex failure of the
     Direct Link Nodes (DLN).

     Following are possible outputs of the three indicators.

       o  First Indicator

            -- ARR UCL:  The ARR will attempt to restore the node
               without running diagnostics.

            -- ARR COND:  The ARR will attempt to restore the node
               but will run diagnostics first.

            -- CNR UCL:  The ARR detects a duplex failure, and
               restoration of the node will be done without running
               diagnostics.

            -- CNR COND:  The ARR detects a duplex failure, and the
               node will undergo diagnostics before restoration.

       o  Second Indicator

            -- ARR RSTRT:  The ARR is restarting the node.

            -- CNR RSTRT:  The ARR detects a duplex failure and is
               restarting the node.

       o  Third Indicator

            -- ACNR UCL:  The ARR detects a duplex failure of the
               DLNs, and an unconditional restoral will be performed
               on the DLN listed.

            -- ACNR COND:  The ARR detects a duplex failure of the
               DLNs, and diagnostics will be run before restoring the
               node.

            -- ACNR RSTRT:  The ARR detects a duplex failure of the
               DLNs and is restarting the DLN listed.

     The upper center area of the display contains information on the
     the status of direct signaling (DSIG), trunk signaling (TSIG),
     and transaction capability (TCAP).  The STATUS box includes the
     following:

       o  DSIG Status:  Following are the DSIG states:

            -- DSIG ACT:  If the GLDSSPEED is 48 and office is
               equipped with 4.8 kbps links, or if the GLDSSPEED is
               560 and office is equipped with 56 kbps links, the
               status indicator block will contain ``DSIG ACT''
               (indicating the appropriate links are active).

            -- DSIG OOS:  If the GLDSSPEED is 48 and the office is
               equipped with 4.8 kbps links, or if the GLDSSPEED is
               560 and the office is equipped with 56 kbps links, and
               the link (4.8 kbps or 56 kbps) is OOS, the status
               indicator block will contain ``DSIG OOS''.

            -- DSIG UNEQ:  If the GLDSSPEED is 48 and the office is
               only equipped with 56 kbps links, or if the GLDSSPEED
               is 560 and the office is only equipped with 4.8 kbps,
               the status indicator block will contain ``DSIG UNEQ''.

            -- DSIG INIT:  If the CNI hardware is performing an
               initialization, the status indicator block will
               contain ``INIT''.  During CNI software
               initializations, CCS call processing is not available,
               and no other information on the display page can be
               considered accurate until the initialization has
               completed.

            -- DSIG DGR:  If signalling is equipped and active, but a
               problem exists (such as signaling link or DLN
               congestion) that may prevent some messages from being
               routed, the status indicator block will contain ``DSIG
               DGR''.

       o  TSIG Status:  Following are the TSIG states:

            -- TSIG ACT:  If the RLPCIPRT relation has tuples
               populated and one of the available links is active,
               the status indicator block will contain ``TSIG ACT''.

            -- TSIG OOS:  If the RLPCIPRT relation has tuples
               populated and all available links are OOS, the status
               indicator block will contain ``TSIG OOS''.

            -- TSIG UNEQ:  If the RLPCIPRT relation has no tuples
               populated, the status indicator block will contain
               ``TSIG UNEQ''.

            -- TSIG INIT:  If the CNI hardware is performing an
               initialization, the status indicator block will
               contain ``INIT''.  During CNI software
               initializations, CCS call processing is not available,
               and no other information on the display page can be
               considered accurate until the initialization has
               completed.

            -- TSIG DGR:  If signalling is equipped and active, but a
               problem exists (such as signaling link or DLN
               congestion) that may prevent some messages from being
               routed, the status indicator block will contain ``TSIG
               DGR''.

       o  TCAP Status:  Following are the TCAP states:

            -- TCAP ACT:  If the RLDS_APP relation has tuples
               populated and the 56 kbps links are active, the status
               indicator block will contain ``TCAP ACT''.

            -- TCAP OOS:  If the RLDS_APP relation has tuples
               populated and the 56 kbps links are OOS, the status
               indicator block will contain ``TCAP OOS''.

            -- TCAP UNEQ:  If the RLDS_APP relation has no tuples
               populated, the status indicator block will contain
               ``TCAP UNEQ''.

            -- TCAP INIT:  If the CNI hardware is performing an
               initialization, the status indicator block will
               contain ``INIT''.  During CNI software
               initializations, CCS call processing is not available,
               and no other information on the display page can be
               considered accurate until the initialization has
               completed.

            -- TCAP DGR:  If signalling is equipped and active, but a
               problem exists [such as signaling link or DLN
               congestion, some (but not all) local subsystems OOS,
               or a pair (but not all pairs) of Global STPs
               inaccessible] that may prevent some messages from
               being routed, the status indicator block will contain
               ``TCAP DGR''.

     The upper right area of the display contains the ALARMS box
     which shows the status of fan, fuse, and power alarms on CNI,
     Digital Facility Access (DFA), and Analog Facility Access (AFA)
     frames.  The ALARMS box also indicates if an alarm is inhibited.
     The three alarm (ALM) indicators are as follows:

       o  FAN ALM:  The CNI frame has three fans located at the
          bottom of the frame cabinet.  When either of the fans stops
          operating at normal RPM frequency, the alarm sounds.
          Normally, this condition is caused by power interruption to
          the fan.  After corrective action has been taken, the
          manual reset button located on the lower right corner of
          the backplane is used is used to reset the fan alarm
          circuitry.

       o  FUSE ALM:  The fuse alarm is triggered when a fuse in the
          CNI equipment blows.  The blown fuse can be in either the
          Ring Node cabinet that furnishes power to nonconverter
          circuits, the AFA cabinet, or the DFA cabinet.  An
          indicator fuse is used to identify the location of the
          blown power fuse.  To replace the power fuse, follow
          guidelines in AT&T 235-105-220, Corrective Maintenance
          Procedures.

       o  PWR ALM:  The power alarm indicates that one of the 495FA
          power converters has lost the ability to furnish power
          because a blown fuse removes power from the converter or
          the converter itself fails.  When this occurs, the node(s)
          associated with that particular converter goes OOS.  If a
          blown power fuse is the cause of the problem, a smaller
          indicator fuse also blows to help identify the bad power
          fuse.  To replace the power fuse, follow guidelines in AT&T
          235-105-220, Corrective Maintenance Procedures.

     The upper right area also contains a DISPLAY section that lists
     pages to access for more information.

     The lower left area of the page contains a multicolumned box
     that shows the major state of the nodes and the minor state of
     the links for each group and member supported.  There are two
     indicators within each member box; the upper is the node major
     state, and the lower is the link minor state.  The major and
     minor states are as follows:

     Node Major States

       o  ACT:  Indicates node is active

       o  OOS:  Indicates node is out of service

       o  STBY:  Indicates node is in standby mode

       o  GROW:  Indicates node is in the growth state

       o  UNEQ:  Indicates node is unequipped.

     Link Minor States

       o  IS:  Indicates link is in service

       o  OOS:  Indicates link is out of service

       o  MOOS:  Indicates link is manual out of service

       o  GROW:  Indicates link is in the growth state

       o  TEST:  Indicates link is being tested

       o  UNAV:  Indicates link is not available.

     When DLNs are equipped, they are assigned to link member 2 in
     the group and are identified by the asterisk (*).  In this case,
     the AP state is displayed in the bottom portion of the box.
     Possible AP states are as follows:

     AP States

       o  ACT:  Indicates AP is active

       o  INIT:  Indicates AP is initializing

       o  OOS:  Indicates AP is out of service

       o  STBY:  Indicates AP is in standby mode.

     The lower right area of the 118 page contains a listing of up to
     10 point codes to which an office has trunking but are
     inaccessible.  All inaccessible point codes are printed on the
     ROP.  If the number of inaccessible point codes exceeds 10, the
     message

          EXCEEDS LIMIT
          SEE ROP

     appears under the listing.

     Any off-normal condition of the nodes or links causes the ``SEE
     PAGE 118'' indicator on the 111/112 page to backlight along with
     the respective node or link indicators on the 118 page.  In the
     SUMMARY STATUS AREA, the AM PERPH critical indicator and the
     alarm level (CRITICAL, MAJOR, or MINOR), if applicable,
     backlights.

     Figure .AW G351/ shows an example of the 118 page.  In this example,
     the number of inaccessible point codes exceeds 10, and the user
     is directed to see the ROP.

     There are no commands on the 118 page.

     All available displays can be accessed from the 118 page.
     The purpose of the 123 display page is to provide status and
     maintenance commands for two disk file controllers (DFC) and up
     to 16 moving head disks (MHD).  It also provides status and
     commands for disk independent operation when both essential
     disks are lost and status of the Auto MHD Configuration feature.

     If there are more than two DFCs in the system, a second DFC
     Status page (Page 125) is used.  The format of the 125 page is
     the same as the 123 except the AUTO MHD CONFIGURATION status is
     not shown; it appears only on Page 123.
     The 123 page has three separate and distinct functions.

     The first function of this page is to provide status and
     maintenance commands for DFCs 0 and 1 and associated MHDs (up to
     16).  If the system is equipped with SCSI, this page also
     provides status and maintenance commands for SBUSes (up to 4).

     The second function is to provide status and commands during
     disk independent operation (DIOP).  When both of the MHDs that
     are marked E (essential) go out of service, this page is
     automatically displayed.  This is called full DIOP.  The
     appropriate menu commands to use under these circumstances are
     the 600 series of commands.  When in full DIOP (Figure .AW G353/), a
     620 command will appear which will allow the MHD to be reloaded
     from tape without bringing down call processing during the
     reading of the tape.  When the MHD has been reloaded, a minimum
     of a 52 boot is required.  The other 600 series commands, with
     the exception of the 699 poke, may be used also when not in
     DIOP.  The 699 poke works only in full DIOP.  Effective in 5E7,
     both the 602 poke to restore the DFC controller and the 604 poke
     to restore the SBUS controller require UCL when the system is in
     full DIOP.  These pokes (602/604) will not restore associated
     subunits (MHDs) to prevent accidental disk restoral during disk
     maintenance.

     If only one of the essential MHDs goes out of service, the MHDs
     are in simplex operation (Figure .AW G352/), but the page is not
     automatically displayed.

     During full DIOP, the area at the bottom of the page between the
     two horizontal lines will display output messages for the 600
     series menu commands.

     The third function of the 123 page is to provide for the display
     of the Automatic MHD Configuration feature.  The AUTO MHD
     CONFIGURATION  data displayed on 123 page is a summary status of
     information from Pages 178, Auto Spare Disk, and 179, Disk
     Configuration.

     Possible values of the Automatic MHD Configuration feature are
     as follows:

       a. AUTO MHD CONFIGURATION READY:  The feature is armed and
          ready to run if needed.

       b. SEE PAGE 179, CONFIG MHDs ...:  The listed MHDs have been
          reconfigured; see Page 179 for more data.

       c. AUTO MHD CONFIGURATION OFF:  The feature is turned off.

       d. MHD CONFIG INHIBITED, SEE PAGE 178:  The feature is blocked
          on one or more MHDs or the entire office; see Page 178 for
          more data.

       e. MHD CONFIG IN PROGRESS, SEE PAGE 178:  An MHD configuration
          is in progress; see Page 178 for more data.

     There are two columns of notations on the right side of each of
     the MHD status columns.  The first of the two columns contains
     one of the following two letters:

       o  Y - (Yes):  This means the MHD was diagnosed or restored
          since the last system initialization and appears to be
          usable.

       o  N - (No):  This means the MHD was not diagnosed or restored
          since the last system initialization and does not appear to
          be usable.

     The second column contains the letter E which signifies that the
     associated MHD is essential.

     The upper two display fields, OPTION LEVEL and CURRENT LEVEL,
     inform the user of the optional disk independent operation
     feature level selected for the operating system and the current
     disk independent operation state the operating system is in.

     The OPTION LEVEL displayed will be one of the following:

       o  NODIOP:  Disk independent operation feature is not
          selected.

       o  UCLDIOP:  Unconditional disk independent operation is
          selected.

     The CURRENT LEVEL displayed will be one of the following:

       o  NORMAL:  Normal operating system without disk independent
          operation mode.

       o  SIMPLEX:  Operating system running with at least one
          essential MHD out of service.

       o  DUPLEX:  Operating system is running with all duplex
          essential MHDs active.

       o  CONDITIONAL DIOP:  Operating system is in conditional disk
          independent operation  mode with the last remaining duplex
          essential MHD about to be removed from service.

       o  FULL DIOP:  Operating system is running with a duplex
          essential pair of MHDs out of service.

     For each unit displayed, the following information is shown:

       o  Major state of the unit

       o  Minor state of the unit (if available)

       o  Usability of the unit (Y = usable, N = unusable)

       o  Essential status of the unit (E = essential, M = manually
          nonremovable, blank = nonessential)

       o  Microcode status (FIRMWARE or PUMPCODE) for the DFC
          (FIRMWARE indicates that there is a problem on PUMPCODE)

       o  Overload status of a DFC.

     Figure .AW G352/ shows the simplex version of the DFC status page for
     an office with SMD only.  In this example, one of the essential
     MHDs (MHD 1) is OOS, so the current level is marked as SIMPLEX.
     The OOS MHD caused the AM PERPH indicator at the top of the page
     to be backlighted.  The automatic MHD configuration feature is
     ready.

     When the simplex mode is entered, the system begins to lock
     essential, nonswappable processes from disk into core (AM
     memory).  Upon completion of the locking process, the system
     will print the message, REPT DIOP SIMPLEX PROCESSING COMPLETED.
     If the system has problems in locking the essential processes
     into core, it will print the message, REPT DIOP SIMPLEX UNSWAP
     FAILURE PID=xx (xx = utility ID of process that failed to lock
     into memory).  This message will reprint every 5 minutes until
     the locking process is completed.

     Figure .AW G353/ shows the FULL DIOP version.

     Figure .AW G354/ shows the duplex version of the DFC status page for
     a 3B21D office with SCSI only or with both SMD and SCSI.

     The only difference between the SCSI and SMD versions of the 123
     page is the addition of ``SBUS 0 SBUS 2'' under DFC 0, ``SBUS 1
     SBUS 3'' under DFC 1 on the SCSI version, and the 604 command
     for RST/RMV SBUS.

     Commands are provided to remove, restore, and diagnose the MHDs
     and to take appropriate actions on the MHDs when one or more
     essential MHDs are out of service.

     All available displays can be accessed from the 123 page.
 2

           CMD         RESULT

           2XX         MHD XX is removed from service
                       (RMV:MHD=XX)
           3XX         MHD XX is restored
                       (RST:MHD=XX)
           5XX         MHD XX is diagnosed
                       (DGN:MHD=XX)
     600,n [v] [s|d]   MHD n is formatted (initialized)
                       (INIT:MHD=n)
                       v=VFY. Verify option to be used (default=no verify
                       option).
                       s=Track number or range of tracks to be initialized
                       (default=all tracks).
                       d=New. The track number or range of tracks and the
                       ``d'' option
                       can only be used for SMD MHD.
        601,n [s]      MHD n is verified
                       (VFY:MHD=n)
                       where s represents either:
                             t=XX (XX is track number or range of tracks
                             to be verified)
                             (default=all tracks for SMD MHD)
                       or
                             b=XX (XX is block number or range of blocks
                             to be verified)
                             (default=all blocks for SCSI MHD)
                       (For example: 601,0 b=80&&100 will cause the
                       VFY MHD function to be invoked for MHD 0 and will
                       verify blocks 80 through 100 for SCSI MHD.)
        602,n [u]      DFC n controller only is restored
                       u=UCL
                       (RST:DFC=n,CONT)
      603,n [t|fn]     Dump MHD n defect table
                       t=Defect table to be dumped:MFGR,COMB,TEMP,
                       ALL,(default=COMB).
                       fn=Full pathname of a file, in double quotes, that the
                       MFGR defect table is to be written to
                       (DUMP:MHD=n:DEFECT)
       604,n a [u]     RESTORE or REMOVE SBUS
                       a=``RST'' or ``RMV''
                       (RST:SBUS=n,CONT)
                       (RMV:SBUS=n)
                       u=UCL

                          Note: For SBUS RST, UCL option is required
                          in full DIOP.

           CMD         RESULT

      605 (RST MHD)    Restore an MHD.  When the system is in FULL DIOP, a
           or          restore will only be allowed if the MHD does not have
        605,n [u]      an active mate and is not marked essential (E).
                       n=MHD number
                       u=UCL
      606 (RST MT)     (3B21D only) Restore a SCSI magnetic tape (MT).
           or          This command is displayed only if a SCSI DFC that
        606.n [u]      supports MT devices is equipped, and it is
                       functionally equivalent to the RST:MT input message.
                       n=MT number
                       u=UCL
         677,n f       Enhanced Information Report (EIR) PRINT
                       n=DFC unit number
                       f=EIR format.  Valid values are ``n''=turn off
                       EIR PRINT, ``l''=long EIR report format,
                       ``s''=short EIR report format
          6XX,h        HELP
                       Gives help for 600 series commands
           688         Clears the buffer
           699         Aborts the menu command that is presently in progress

                          Note:  The 699 poke appears only while
                          the system disk is in full DIOP.  It is not
                          effective in normal or simplex modes.

       620,n td a      Loads MHD n from tape drive td using sequence a
                       td=Tape device name
                       a=BOTH,GEN,DBONLY or CONT.

                          Note:  The 620 poke appears only while
                          the system disk is in full DIOP.  It is not
                          effective in normal or simplex modes.


       Note:   The 600 series commands work while the system disk
               is in full DIOP except that pokes 602 (DFC
               controller only restore), 604 (SBUS controller only
               restore), 605 (MHD restore), and 606 (SCSI MT
               restore) require UCL.

     The purpose of the 125 display page is to provide status and
     maintenance commands for two DFCs and up to 16 moving head disks
     (MHD).  It also provides status and commands for disk
     independent operation when both essential disks are lost.

     This page exists only when there are more than two DFCs in the
     system.

     The format of the 125 page is the same as the 123 except the
     AUTO MHD CONFIGURATION status is not shown; it appears only on
     Page 123.
     The 125 page has two separate and distinct functions.

     The first function of this page is to provide status and
     maintenance commands for DFCs 2 and 3 and associated MHDs (up to
     16).

     The second function is to provide status and commands during
     disk independent operation (DIOP).  When in full DIOP, the 125
     page will be accessible.  The 620 poke (reload from tape option)
     will only work on the 123 page.  The other 600 series commands,
     with the exception of the 699 poke, may be used also when not in
     DIOP.  The 699 poke works only in full DIOP.  Effective in 5E7,
     both the 602 poke to restore the DFC controller and the 604 poke
     to restore the SBUS controller require UCL when the system is in
     full DIOP.  These pokes (602/604) will not restore associated
     subunits (MHDs) to prevent accidental disk restoral during disk
     maintenance.

     If only one of the essential MHDs goes out of service, the MHDs
     are in simplex operation (Figure .AW G355/), but the page is not
     automatically displayed.

     During full DIOP the area at the bottom of the page between the
     two horizontal lines will display output messages for the 600
     series menu commands.

     There are two columns of notations on the right side of each of
     the MHD status columns.  The first of the two columns contains
     one of the following two letters:

       o  Y (Yes):  This means the MHD was diagnosed or restored
          since the last system initialization and appears to be
          usable.

       o  N (No):  This means the MHD was not diagnosed or restored
          since the last system initialization and does not appear to
          be usable.

     The second column contains the letter E which signifies that the
     associated MHD is essential.

     Figure .AW G355/ shows the simplex version of the disk file controller
     status page for an office with SMD only.  In this example, one
     of the essential MHDs (MHD 17) has gone out of service, so the
     current level is marked as SIMPLEX.  The OOS MHD caused the AM
     PERPH indicator at the top of the page to be backlighted.

     When the simplex mode is entered, the system begins to lock
     essential, nonswappable processes from disk into core (AM
     memory).  Upon completion of the locking process, the system
     will print the message, REPT DIOP SIMPLEX PROCESSING COMPLETED.
     If the system has problems in locking the essential processes
     into core, it will print the message, REPT DIOP SIMPLEX UNSWAP
     FAILURE PID=xx (xx = utility ID of process that failed to lock
     into memory).  This message will reprint every 5 minutes until
     the locking process is completed.

     Commands are provided to remove, restore, and diagnose the MHDs
     and to take appropriate actions on the MHDs when one or more
     essential MHDs are out of service.

     All available displays can be accessed from the 125 page.
 2

           CMD         RESULT

           2XX         MHD XX is removed from service
                       (RMV:MHD=XX)
           3XX         MHD XX is restored
                       (RST:MHD=XX)
           5XX         MHD XX is diagnosed
                       (DGN:MHD=XX)
     600,n [v] [s|d]   MHD n is formatted (initialized)
                       (INIT:MHD=n)
                       v=VFY. Verify option to be used (default=no verify
                       option).
                       s=Track number or range of tracks to be initialized
                       (default=all tracks).
                       d=New. The track number or range of tracks and the
                       ``d'' option can only be used for SMD MHD.
        601,n [s]      MHD n is verified
                       (VFY:MHD=n)
                       where s represents either:
                             t=XX (XX is track number or range of tracks
                             to be verified)
                             (default=all tracks for SMD MHD)
                       or
                             b=XX (XX is block number or range of blocks
                             to be verified)
                             (default=all blocks for SCSI MHD)
                       (For example: 601,0 b=80&&100 will cause the
                       VFY MHD function to be invoked for MHD 0 and will
                       verify blocks 80 through 100 for SCSI MHD.)
        602,n [u]      DFC n controller only is restored
                       u=UCL
                       (RST:DFC=n,CONT)
      603,n [t|fn]     Dump MHD n defect table
                       t=Defect table to be dumped:MFGR,COMB,TEMP,
                       ALL,(default=COMB).
                       fn=Full pathname of a file, in double quotes, that the
                       MFGR defect table is to be written to
                       (DUMP:MHD=n:DEFECT)
       604,n a [u]     RESTORE or REMOVE SBUS
                       a=``RST'' or ``RMV''
                       (RST:SBUS=n,CONT)
                       (RMV:SBUS=n)
                       u=UCL

                          Note: For SBUS RST, UCL option is required
                          in full DIOP.

           CMD         RESULT

      605 (RST MHD)    Restore an MHD.  When the system is in FULL
           or          DIOP, a restore will only be allowed if the MHD
         605,n [u]     does not have an active mate and is not marked
                       essential (E).
                       n=MHD number
                       u=UCL
      606 (RST MT)     (3B21D only) Restore a SCSI MT.  This command
           or          is displayed only if a SCSI DFC that supports
        606,n [u]      MT devices is equipped, and it is functionally
                       equivalent to the RST:MT input message.
                       n=MT number
                       u=UCL
         677,n f       Enhanced Information Report (EIR) PRINT
                       n=DFC unit number
                       f=EIR format.  Valid values are ``n''=turn off
                       EIR PRINT, ``l''=long EIR report format,
                       ``s''=short EIR report format
          6XX,h        HELP
                       Gives help for 600 series commands
           688         Clears the buffer
           699         Aborts the menu command that is presently in progress

                          Note:  The 699 poke appears only while
                          the system disk is in full DIOP.  It is not
                          effective in normal or simplex modes.

       620,n td a      Loads MHD n from tape drive td using sequence a
                       td=Tape device name
                       a=BOTH,GEN,DBONLY or CONT.

                          Note:  The 620 poke appears only while the
                          system disk is in full DIOP.  It is not effective
                          in normal or simplex modes.


       Note:   The 600 series commands work while the system disk
               is in full DIOP except that pokes 602 (DFC
               controller only restore), 604 (SBUS controller only
               restore), 605 (MHD restore), and 606 (SCSI MT
               restore) require UCL.

     The 126 display page provides the optional disk file controller
     performance data.

     Page 126,the DFC performance page, shows data for a maximum of
     two DFCs.  If there are more than two DFCs in the system, a
     second DFC performance page (Page 128) is used.

     The 126 page can show either SMD or SCSI, depending on the
     feature option of the operational office.

     With the SCSI feature, the DFC performance data is not available
     when the operating system is in disk independent operation
     (DIOP) mode.

     Meanings of the performance fields displayed are as follows:

       o  CMP:  Jobs completed by the DFC for the unit.  This field
          is normalized to show the number of jobs that were
          completed per second.

       o  AVG:  The average size of the jobs completed for a unit
          (number of disk blocks).

       o  MAX:  The maximum size of a job completed in a time
          interval (number of disk blocks).

     Figure .AW G356/ shows an example of the 126 display page for an
     office with SMD only.

     Figure .AW G357/ shows an example of the 126 page with mixed SMD and
     SCSI DFCs for a 3B21D office.

     The DFC fields are the sum of the individual MHD fields
     associated with the DFC.  For SCSI DFC, the SBUS fields are the
     sum of all the MHD fields associated with this SBUS.

         CMD       RESULT

     622[,s [t]]   Performance updates are displayed
                   s = number of seconds between performance updates.
                   Valid number of seconds is between 1 and 60.  Performance
                   updates will occur 20 times, then will be automatically
                   turned off.  If s is zero or is defaulted, then
                   performance updates are turned off.
                   t = number of times to repeat the performance updates.
         688       The 3-line communication area at the bottom of the
                   page is cleared.
         6XX,h     Gives help for 600 series commands
     The 128 display page provides the optional disk file controller
     performance data.

     Page 126,the DFC performance page, shows data for a maximum of
     two DFCs.  If there are more than two DFCs in the system, a
     second DFC performance page (Page 128) is used.  The 128 page is
     used only when there are more than two DFCs in the system.

     The 128 page can show either SMD or SCSI, depending on the
     feature option of the operational office.

     With SCSI feature, the DFC performance data is not available
     when the operating system is in disk independent operation
     (DIOP) mode.

     Meanings of the performance fields displayed are as follows:

       o  CMP:  Jobs completed by the DFC for the unit.  This field
          is normalized to show the number of jobs that were
          completed per second.

       o  AVG:  The average size of the jobs completed for a unit
          (number of disk blocks).

       o  MAX:  The maximum size of a job completed in a time
          interval (number of disk blocks).

     Figure .AW G358/ shows an example of the 128 display page with full
     SCSI DFCs.

         CMD       RESULT

     622[,s,[t]]   Performance updates are displayed
                   s = number of seconds between  performance updates.
                   Valid number of seconds is between 1 and 60.  Performance
                   updates will occur 20 times, then will be automatically
                   turned off.  If s is zero or is defaulted, then
                   performance updates are turned off.
                   t = number of times to repeat the performance updates.
         688       The 3-line communication area at the bottom of the page
                   is cleared.
        6XX,h      HELP
                   Gives help for 600 series commands

     The 130 display page provides status of the manual and automatic
     NM system controls and status of NM circuit conditions. Also, it
     provides a command to get a listing of any NM controls that are
     YES.
     When there is an overload in the system there are manual or
     automatic controls that can be put on the system by Network
     Management. The 130 page shows the status of these controls,
     either YES or NO.

     Any controls on this page that are YES will cause an indicator
     that refers to this page to appear and be backlighted on Page
     109 - OVERLOAD. In the STATUS SUMMARY AREA at the top of the
     screen, the OVERLOAD status summary indicator will be
     backlighted. This page also has a reference back to Page 109
     that is displayed all the time.

     Figure .AW G359/ shows there is a manual control on the CALL GAP and
     transmit (XMT) of dynamic overload control (DOC) and direct link
     node (DLN) are allowed (ALW).

     The command on this page is provided to print a listing of any
     NM controls that are YES. Also, any available paging commands
     can be entered from this display.

     CMD   RESULT

     900   Any YES NM controls are output (OP:NMPGE)

     The hardware call trace page displays (133 through 138) show the
     hardware paths of calls requested to be traced.
     Call Trace Pages 133 through 138 provide a ``snapshot'' of the
     hardware and software path(s) involved with a call.  Page 133 is
     the main UTILITY CALL TRACE display.  Some calls require several
     displays, for example, a 3-way call.  A ``SEE PAGE'' indicator
     appears if more displays are involved in a particular call.

     Information collected about dynamic data structures and hardware
     paths can aid in trouble-shooting a failed call.  The software
     state, external identifier, peripheral path, and network path
     are shown for each connection of the call and are described as
     follows:

       o  Software state:  The software state represents the state of
          the call (ringing, talking, transient, etc.) as stored in
          the process control block link area (PCBLA).

       o  External identifier:  The external identifier is the
          representation of the customer and can include the
          following:

            -- Directory Number (DN)

            -- Multiline Hunt Group (MLHG) group and member

            -- Trunk (TRK) group and member

            -- Equipment Number (EN).

       o  Peripheral path:  The peripheral path displays the hardware
          path taken by the call from the peripheral unit through the
          service units to the Time Slot Interchanger (TSI).

       o  Network path:  The network path is represented by the
          Network Control and Timing (NCT) time slot connecting the
          TSI to the Time Multiplexed Switch (TMS).  The connection
          from the NCT to the TMS is shown as either a solid line,
          representing an inter-SM call, or a dotted line,
          representing an intra-SM call.

     If an ISDN call is traced, the type of circuit switched service
     (voice or data) and a B-channel identifier (B-1, B-2, or ON
     HOLD) are displayed.  The ON HOLD means that no B-channel is
     allocated for the call.

     The ISDN calls that have been parked will display ON HOLD,
     because parking a call releases the B-channel.  Analog calls
     that have been parked will display PARKED.  Peripheral path
     information may not be available for parked calls.

     For an OSPS call through a remote ISLU (RISLU), the connection
     via a T1 carrier between the DLTU remote (DLTUR) in the RISLU
     and the DLTU host (DLUTH) in the switch will be shown.
     Additionally, if business and residence custom services (BRCS)
     features are assigned to a DSL, the primary directory number
     (PDN), subaddress (SA), and call appearance (CA) will be
     displayed.

     For 5E8 and later software releases, standard ISDN DSLs are
     supported.  If a standard EKTS DSL is traced, the SA and CA are
     displayed as for a custom DSL.  If a standard non-EKTS is
     traced, SA and CA do not apply.

     The Integrated Digital Carrier Unit (IDCU) is also supported for
     5E8 and later software releases.  Call Trace displays the SM and
     IDCU numbers for an IDCU.

     The IDCU peripheral unit contains a time slot interchange unit
     (TSIU) which offers the ability to make connections without
     using the TSI in the SM, thus saving SM time slot resources.  A
     trace of this hairpin connection only shows the RT and the IDCU.

     The IDCU also supports the PUB43801 interface format used for
     interfacing to D4 and D5 channel banks and to Digital Access
     Cross Connect Systems (DACS).  Since these connections do not
     use an RT, RT is not shown on the trace.  The FAC field in an
     IDCU display contains the IDCU facility (IFAC) number.

     In 5E9(1) and later software releases, the intercom (ICOM) group
     number is included in the call trace output.  A call appearance
     (CA) ICOM call does not have a DN associated with it.  A trace
     of this type of call displays the ICOM group number where the DN
     is normally displayed.  A ``feature button'' ICOM call has an
     associated DN which is displayed at the MCC.  The ICOM group
     number is printed on the ROP output message for both types of
     ICOM calls.

     Also in 5E9(1) and later, a wideband indicator (WB) is displayed
     when a call using more than one timeslot is traced.  The
     OP:CHANMAP command can be used to determine the other timeslots
     active on the call.

     Examples of Hardware Call Trace displays are as follows:

       o  Figure .AW G360/ - Multipoint DSL to ISDN PODS

       o  Figure .AW G361/ - Fractional DS1 Switching

       o  Figure .AW G362/ - Analog DN to an Analog Trunk

       o  Figure .AW G363/ - Hairpinned IDCU PUB43801

       o  Figure .AW G364/ - OSPS OPT

       o  Figure .AW G365/ - RSM Inter Cluster Link (ICL)

       o  Figure .AW G366/ - Subscriber Loop Carrier to Analog IDCU DN

       o  Figure .AW G367/ - Call Appearance ICOM (CAICOM)

       o  Figure .AW G368/ - Parked Analog Call

       o  Figure .AW G369/ - RSM to HSM.

     Refer to 131 - Call Trace Menu display (Figure .AW G319/) for the
     complete list of call traces that can be invoked (by poke
     commands) from the 133 through 138 page displays.  Also, all
     available page displays can be invoked from the 133 through 138
     page displays.
     The 151 page display shows the hardware paths to the conference
     circuit when a conference call is traced.
     Conference circuits are located in the Global Digital Service
     Unit (GDSU) and provide 3-port or 6-port customer service
     conferencing capabilities for an office.  The maximum number of
     hardware paths for 3-port and 6-port conference circuits is 3
     and 6 respectively.

     When calls involving more than one conference circuit are
     traced, only the first conference circuit found is displayed.  A
     multiple-conference circuit call is identified by the existence
     of an associate conference controller, or an associate floating
     conference controller, in the TRC UTIL LINE output message on
     the ROP.  To view the connections of the other conference
     circuits on the call, trace the associate conference controllers
     found in the TRC UTIL LINE output message, using the PID option
     on the TRC UTIL input message.

     Multiple-conference circuit calls can also be the result of an
     ACD/BRCS Service Observe connection set up on a multiway call.
     Again, only the first conference circuit found is displayed.  To
     view the connections of the other conference circuits on the
     call, trace the associate conference controller or the
     monitoring PID found in the TRC UTIL LINE output message.
     Tracing the monitoring PID will ensure that the conference
     circuit used to set up the Service Observe connection is
     displayed.

     The NCT time slot numbers have the format ``aaa bbb'' for an
     intramodule path on the conference circuit SM.  For an
     intermodule path between SM ``ddd'' and the conference circuit
     SM, the format is ``ccc SM=ddd''.  The letter ``A'' next to the
     SM number indicates that automatic time slot switching
     (AUTISSING) has occurred.  AUTISSING is a failure with the E-bit
     data on the major side of the TMS.  Therefore, the time slot
     number represented in this situation is from the minor side of
     the TMS.

     For ACD/BRCS Service Observe connections, the NCT time slot
     numbers displayed on the 151 page may not match the NCT time
     slot numbers displayed on the 133-138 pages.  This is due to the
     TSI channel looping used to set up Service Observe calls.
     Information on the looped channels can be obtained by using the
     450 poke to dump the dynamic data associated with the Monitoring
     Bridge.

     All of the dynamic data associated with the traced conference
     circuit can be dumped to the ROP from any call trace page by
     using the 450 poke and the PID of the conference circuit process
     or STRUCTS=confckt.

     A ``SEE PAGE'' indicator in the upper right corner of the 151
     page identifies associated page displays to access for
     additional call trace information.

     Figure .AW G370/ shows an example of the 151 page display.  In this
     example, the indicator ``SEE PAGES 133, 134, 135'' directs the
     user to the 133, 134, and 135 pages for more details.

     Refer to Page 131 - Call Trace Menu (Figure .AW G319/) and Page 132 -
     Call Trace Menu Cont. (Figure .AW G320/) for the complete list of call
     trace poke commands that can be invoked.  Also, any call trace
     display page can be accessed from the 151 display page.
     The 170 display page provides detailed overload information for
     the AM, CMP, DLN (if equipped), and SM(s).
     Any AM or DLN overload conditions are shown on the 170 display
     page.  If a DLN overload occurs, the DLN group and member number
     will be shown as well as the type of overload.

     Details on an SM overload can be obtained by entering poke
     1300,X, DISPLAY SM X OVERLOAD INFO.  Likewise, details on a CMP
     overload can be obtained by entering poke 1370,X, DISPLAY PRIM
     CMP X OVERLOAD INFO, or poke 1371,X, DISPLAY MATE CMP X OVERLOAD
     INFO.

     The REALTIME overload indicators will contain NONE, MINOR,
     MAJOR, or CRIT to show the severity of the overload. NONE means
     no overload exists. MINOR and MAJOR are different levels of
     real-time overloads. Critical (CRIT) is only used for DLNs and
     SMs and is the most severe type of overload.

     For RESOURCE overloads, either NONE or the name of the resource
     will be displayed. The monitored resources are as follows:

       o  MCB - Message Control Block

       o  PCB - Process Control Block

       o  RCV - Tone Receivers (SM only)

       o  SCB - Stack Control Block

       o  TCB - Timer Control Block

       o  PKB - Packet Buffers [operator services position system
          (OSPS) SMs only]

       o  PSU - Packet Switch Unit (Packet Switching SMs only)

       o  ADB - Analog Data Block (SM only)

       o  APB - Associated Process Block (SM only)

       o  BRCSDB - Business and Residence Custom Services (BRCS) Data
          Block (SM only)

       o  CBDB - Call Buildup Data Block (SM only)

       o  CCBCOM - Channel Control Block Communication Region (SM
          only)

       o  CHDB - Channel Data Block (SM only)

       o  CLDB - Calling Leg Data Block (SM only)

       o  CPLR - Coupler (SM only)

       o  DALB - D-Channel Application Linkage Block (SM only)

       o  DIB - DSL Input Buffer (SM only)

       o  EDIB - Extended DSL Input Buffer (SM only)

       o  DISPDB - Display Data Block (SM only)

       o  DLNPIC - DLN to PIC Message Buffer (DLN only)

       o  E911DB - Enhanced 911 Data Block (SM only)

       o  LSCMDB - Large Shared Call Model Data Block (SM only)

       o  MDB - Model Data Block (SM only)

       o  MSG - Message Overflow (because of PIC overload)

       o  PHDB - Path Data Block (SM only)

       o  PICDLN - PIC to DLN Message Buffer (DLN only)

       o  RRB - Ring Receive Buffer (DLN only)

       o  SCMDB - Shared Call Model Data Block (SM only)

       o  TSDB - Time Slot Data Block (SM only)

       o  PSIB - X-25 Packet Switch Input Buffer (SM only)

       o  IAQ - CMP Input Queue (CMP only).

     The AM and DLN information boxes contain information regarding
     real-time and resource overloads in the AM and DLN respectively.

     Figure .AW G371/ shows an example of the 170 display page with the AM
     in SCB resource overload and DLN 00-2 in RRB overload.  Poke
     1300,5 is used to display overload information for SM 5.  The SM
     5 is shown in MINOR real-time overload and EDIB resource
     overload.

     Similarly, CMP information is displayed on request by poke
     1370,X for the primary CMP and poke 1371,X for the mate CMP
     (where X = CMP number).

     Figure .AW G372/ shows an example of the 170 page where poke 1370,0 is
     used to display overload information on primary CMP 000.  In
     this example, primary CMP 000 is in MAJOR real-time overload and
     PCB resource overload.  Also shown is the AM in SCB resource
     overload and DLN 00-2 in RRB resource overload.

     Commands are provided to obtain detailed information on SM and
     CMP overload conditions.

     In addition to these commands, any available paging command can
     be entered from Display Page 170.

      CMD     RESULT

     1300,X   SM X Overload Information is displayed
     1370,X   Primary CMP X overload information is displayed
     1371,X   Mate CMP X overload information is displayed
     The 1520 display page provides information about the Common
     Network Interface (CNI) nodes, groups, and members.
     The 1520 page reflects information taken by reading the
     equipment configuration data (ECD) to find the state of all
     equipped nodes after the Interprocess Message Switch (IMS) has
     finished initialization.  The page should not be displayed until
     after the IMS has finished initializing.  Although the display
     exists, it does not show valid information while the IMS driver
     is not running or is in the process of initializing.  Page 118
     status indicates when CNI is in initialization.

     Only the RING STAT indicator, MAJOR STATE indicator, and the
     function that was executed are backlighted.

     The page is dynamic in that the page is updated and redrawn each
     time the ring configures to a new major stable state.

     Nodes are displayed in one of four modes determined by commands.
     The commands and their respective modes are as follows:

       o  400:  BISO-EISO (beginning isolation-ending isolation)
          (Display an isolated segment)

       o  401/402:  ALL NON-ACT NEXT/PREV  (Display all nonactive
          nodes)

       o  403/404:  ALL EQUIPPED NEXT/PREV  (Display all equipped
          nodes)

       o  6NN:  DISPLAY GROUP NN  (Display group number NN).

     The ALL NON-ACT and ALL EQUIPPED displays may be oriented to
     begin at any equipped starting node by using the up/down cursor
     to go to the NODE< prompt where a starting node can be entered.
     Also, manual nodes may be entered on the ALL NON-ACT and ALL
     EQUIPPED pages by using the up/down cursor to go to the list of
     nodes where a node name may be entered on any line. The line
     number for these manual entries are then highlighted to
     distinguish them from the regular nodes of the display.

     The 1520 page is divided into two basic areas: left side and
     right side.

     Left-side indicators show the ring major state and restore
     activity of the ARR subsystem of IMS.  Also listed on the left
     side are commands and their functions.

     The ring status indicator displays the state of the CNI ring.
     Possible RING STAT states are as follows:

       o  ACTIVE:  Indicates all nodes are active.

       o  DOWN:  Indicates a critical problem; no CCS call processing
          can be completed.

       o  RESTORE:  Indicates node is being pumped and should soon go
          ACTIVE.

       o  CONFIGURING:  Indicates ring has just RESTORED a node, and
          the ring is propagating the token to allow the node back
          into service with the rest of the ring.

       o  ISOLATED SEGMENT:  Indicates ring has one or more nodes
          under diagnostics; requires a quarantine or isolation of
          the node.

     The ARR has three indicators which appear in the top left of the
     1520 page under RING STAT.  The ARR indicators show the type of
     recovery being done and which node is currently being worked on.
     Following are possible outputs of the three ARR indicators.

       o  First Indicator

            -- ARR UCL:  The ARR will attempt to restore the node
               without running diagnostics.

            -- ARR COND:  The ARR will attempt to restore the node
               but will run diagnostics first.

            -- CNR UCL:  The ARR detects a duplex failure and
               restoration of the node will be done without running
               diagnostics.

            -- CNR COND:  The ARR detects a duplex failure and the
               node will undergo diagnostics before restoration.

       o  Second Indicator

            -- ARR RSTRT:  The ARR is restarting the node.

            -- CNR RSTRT:  The ARR detects a duplex failure and is
               restarting the node.

       o  Third Indicator

            -- ACNR UCL:  The ARR detects a duplex failure of the
               DLNs, and an unconditional restoral will be performed
               on the DLN listed.

            -- ACNR COND:  The ARR detects a duplex failure of the
               DLNs, and diagnostics will be run before restoring the
               node.

            -- ACNR RSTRT:  The ARR detects a duplex failure of the
               DLNs and is restarting the DLN listed.

     Information shown on the right side of the page is in the form
     of a tabular listing of nodes with indicators for node name,
     ring position, major state, ring interface state, node processor
     state, and maintenance mode.  Possible values for these
     indicators are as follows:

       o  RING POS

            -- ISO:  Indicates node is isolated.

            -- BISO:  Indicates node is beginning isolation.

            -- EISO:  Indicates node is ending isolation.

            -- NORM:  Indicates node is normal.

            -- ``blank'':  Indicates unequipped.

       o   MAJOR STATE

            -- ACT:  Indicates node is active.

            -- OOS:  Indicates node is out of service.

            -- STBY:  Indicates node is in standby mode.

            -- GROW:  Indicates node is in the growth state.

            -- UNEQ:  Indicates node is unequipped.

            -- UNAV:  Indicates node is unavailable.

            -- INIT:  Indicates node is initializing.

            -- OFL:  Indicates node is off-line.

       o  RI STATE

            -- FLTY:  Indicates node is faulty.

            -- USBL:  Indicates node is usable.

            -- QUSBL:  Indicates node is quarantine usable.

            -- UNTSTD:  Indicates the node is untested.

       o  NP STATE

            -- FLTY:  Indicates node is faulty.

            -- USBL:  Indicates node is usable.

            -- UNTSTD:  Indicates node is untested.

       o  MAINT MODE

            -- AUTO:  Indicates node is automatic.

            -- MAN:  Indicates node is manual.

            -- FLTY:  Indicates node is faulty.

            -- XTHD:  Indicates node is threshold exceeded.

     Figure .AW G373/ shows an example of the 1520 page.  In this example,
     the RING STAT is ISOLATED SEGMENT, LN00 1's MAJOR STATE is OOS
     and backlighted, the MAJOR STATE for RPCN00 0, LN00 2, and LN00
     3 are ACT, and the function is DISPLAY GROUP NN.  (Although RING
     STAT, MAJOR STATE(s), and FUNCTION executed are backlighted,
     only the abnormal MAJOR STATE condition (OOS) is backlighted in
     the example.)

 2
         CMD       RESULT

         2XX       Remove the node listed at line XX.
         3XX       Restore unconditionally the node listed at line XX.
         400       Display a listing of up to 16 nodes of an isolated
                   segment beginning with the BISO node and ending with
                   the EISO node.  If the isolated segment is greater than
                   16 nodes, the display shows the BISO node and the seven
                   nodes following it plus the eight nodes leading up to
                   and including the EISO node.  The missing portion of
                   the isolated segment can be accounted for under the
                   TOTAL BISO-EISO NODES listed at the bottom left-hand
                   corner of the page.
       401/402     Display all nonactive nodes (up to 16). The missing
     (NEXT/PREV)   portion of the list can be accounted for under the
                   TOTAL NON ACTIVE NODES:nn. The count nn is updated as
                   any node changes between the active and nonactive states.
       403/404     Display all equipped nodes (up to 16).
     (NEXT/PREV)   The missing portion of the list can be accounted for
                   under the TOTAL EQUIPPED NODES:nn. The count nn is
                   updated as any node changes between the equipped and
                   unequipped states.
         500       Diagnose the existing isolated segment.
         5XX       Diagnose the node listed at line XX.
         6NN       Display ring group NN, including nonequipped nodes (up
                   to 16).  The missing portion of the list can be accounted
                   for under the TOTAL EQUIPPED NODES:nn. The count nn is
                   updated as any node changes between the equipped and
                   unequipped states.
         7XX       Restore conditionally the node listed at line XX.

     The 1521,XX display page provides information on an individual
     ``group'' of signaling links, where XX is the group member.  The
     ``group'' in these descriptions refers to the set of (up to)
     eight links displayed on the page.
     The following link group status information is provided on the
     1521,XX display page:

       o  NODE NAME (GRP MEM):  Group and member number.  (The NODE
          NAME indicator backlighting reflects the node major state
          for that group and member as it appears on Pages 118 and
          1520.)

       o  FAR END CLLI :  Far-end CLLI code.  (Backlighting is the
          same as that of the MINOR STATE indicator.)

       o  PROT TYPE:  CCS protocol type (6 or 7).  (Backlighting is
          the same as that of the MINOR STATE indicator.)

       o  LINK TYPE:  (Backlighting is the same as that of the MINOR
          STATE indicator.)

       o  MATE NODE:  For mated links, the group and member of the
          banded mate. (Backlighting is the same as that of the MINOR
          STATE indicator.)

       o  MAJOR STATE:  MAJOR STATE can be one of the following:
          (Backlighting is the same as that of the MINOR STATE
          indicator.)

            -- AVAL:  Indicates link is available

            -- UNAV:  Indicates link is not available

            -- UNEQ:  Indicates link is unequipped.

       o  MINOR STATE:  Minor state can be one of the following:

            -- IS:  Indicates link is in service

            -- OOS:  Indicates link is out of service

            -- MOOS:  Indicates link is manual out of service

            -- GROW:  Indicates link is in the growth state

            -- TEST:  Indicates link is being tested

            -- UNAV:  Indicates link is not available.

       o  PRO RCVD:  The processor outage received from the signal
          transfer point is either YES or NO.  (Backlighting is the
          same as that of the MINOR STATE indicator.)

     A situation may occur where the IMS subsystem has changed the
     hardware state of the link, as in growth procedure or ring
     failure, and has not yet notified the CNI subsystem that the
     change has taken place.  In this instance, the 5ESS switch will
     not be notified of the change, and the 1522 page may show old or
     out-of-date status when compared to the IMS display pages (Page
     1520 and a part of Page 118 are updated first).  The user should
     always assume the IMS display page has the correct status.  In
     this case, the user should specifically poke the page with the
     link group and force the 5ESS switch to redisplay the most
     current information for that link group.

     Figure .AW G374/ shows an example of the 1521 page.  In this example,
     LN00 1 and LN00 3 have a MAJOR STATE of AVAL and a MINOR STATE
     of MOOS.  All link group status information is backlighted to
     reflect the MINOR STATE condition.

     The 1521 page provides commands to remove, restore, and diagnose
     the links nodes (LN).

     CMD    RESULT

     2XXY   LN XXY is diagnosed (RMV:LNXX=Y)
            (where XX=group being displayed, Y=member)
     3XXY   LN XXY is diagnosed (RST:LNXX=Y,RAW,TLP)[,UCL]
            (where XX=group being displayed, Y=member)
     5XXY   LN XXY is diagnosed (DGN:LNXX=Y,RAW,TLP)[,RPT=a][PH=b[&&c]]
            (where XX=group being displayed, Y=member)
            ``a'' is the number of times the diagnostic is to be repeated
            ``b'' is the phase
            ``b&&c'' is the range of the phases to be performed
     900    Status of the RING is printed (OP:RING:DETD)
     901    Status of all signaling links are printed (OP:SLK=ALL,DEST=1)

     The purpose of the 1522,XX,Y page is to provide information on a
     specific CNI signaling link (SLK) (where XX is the group number,
     and Y is the member number).
     Information shown on the 1522,XX,Y page includes the following:

       A. LOCAL STATES:  Refers to the link member status which can
          be MAJOR, MINOR, or HDWR.  (Only the LOCAL STATES
          indicators are backlighted.)

            o  MAJOR STATE:  Major state indicators are as follows:

                 -- AVAL:  Indicates link is available

                 -- UNAV:  Indicates link is not available

                 -- UNEQ:  Indicates link is unequipped.

            o  MINOR STATE:  Minor state indicators are as follows:

                 -- IS:  Indicates link is in service

                 -- OOS:  Indicates link is out of service

                 -- MOOS:  Indicates link is manual out of service

                 -- GROW:  Indicates link is in the growth state

                 -- TEST:  Indicates link is being tested

                 -- UNAV:  Indicates link is unavailable.

            o   HDWR:  The hardware state is displayed as follows:

                 -- IS:  Indicates link is in service

                 -- OOS:  Indicates link is out of service.

       B. NODE NAME:  Group and member number.  (The NODE NAME
          indicator backlighting reflects the node major state for
          that group and member as it appears on Pages 118 and 1520.)

       C. LINK PROTOCOL:  Link Protocol is either 6 for CCS6 or 7 for
          CCS7.

       D. RECENT CHANGEABLE INFORMATION:  The following recent change
          information is displayed:

            o  ENCRYPTED:  Encryption type for link is NOTENC (not
               encrypted) or ENC (encrypted).

            o  LINK TYPE:  Link type A for A-links and E for E-links.

            o  SPEED:  Speed of the link (48 for 4.8 kbps or 560 for
               56 kbps).

            o  FACILITY:  Facility is ONLY for CCS7 (MODEM).

            o  MATE:  Mate SLK is displayed by group and member.

            o  DIRECT LS:  Direct link set numbers for CCS7.

            o  COMBINE LS:  Pool link set numbers for CCS7.

            o  EC_MODE:  Error correction mode is ONLY for CCS7
               (BASIC).

            o  TRANS MEDIUM:  Transmission medium is ONLY for CCS7
               (TERRESTRIAL for cable connected).

            o  FAR END CLLI CODE:  An 11-character identifier
               containing various office-specific information such as
               city, state, and machine type.

            o  FAR END FUNCTION NO:  A 5-digit number uniquely
               identifying the far-end node in the network.

            o  FAR END POINT CODE:  A 9-digit number that identifies
               the far-end STP.

            o  FAR END REGION NO:  A 2-digit number that identifies
               the far-end region.

     The situation may occur where the IMS subsystem has changed the
     hardware state of the link, as in growth procedure or ring
     failure, and has not notified the CNI subsystem that the change
     has taken place.  In this instance, the 5ESS switch will not be
     notified of the change, and the 1522 page may show old or out-
     of-date status when it is compared to the IMS display pages
     (Page 1520 and part of Page 118 are updated first).  The user
     should always assume the IMS display page has the correct
     status.  In this case, the user should specifically poke the
     page with the link group and force the 5ESS switch to redisplay
     the most current information for that link group.

       Note:   In some cases, the IMS subsystem does not notify
               CNI that a link hardware state has changed. The
               user should always assume that the IMS display Page
               1520 has the correct status.

     Figure .AW G375/ is an example of the 1522 page showing that link node
     00-1 has a MAJOR state of AVAL, a MINOR state of MOOS, and a
     HDWR state of OOS.  Although all LOCAL STATES are backlighted,
     only the indicators showing abnormal conditions (OOS and MOOS)
     are backlighted in this example.

     The 1522 page provides commands to remove, restore, and diagnose
     the links.

      CMD    RESULT

     2XXY    LN XXY is diagnosed (RMV:LNXX=Y)
             (where XX=group being displayed, Y=member being displayed)
     3XXY    LN XXY is diagnosed (RST:LNXX=Y,RAW,TLP)[,UCL]
             (where XX=group being displayed, Y=member being displayed)
     5XXY    LNxxy is diagnosed (DGN:LNXX=Y,RAW,TLP)[,RPT=a][PH=b[&&c]]
             (where XX=group being displayed, Y=member being displayed)
             ``a'' is the number of times the diagnostic is to be repeated
             ``b'' is the phase
             ``b&&c'' is the range of the phases to be performed
     41XXY   Monitor ON  (MON:SLK=XX-Y,ON)
             (where XX=group being displayed, Y=member being displayed)
     42XXY   Monitor OFF (MON:SLK=XX-Y,OFF)
             (where XX=group being displayed, Y=member being displayed)

     The 1523 page provides the status of all local subsystems of the
     5ESS switch.
     Subsystem status information provided on the 1523 page is as
     follows:

       o  POINT CODE:  The point code number of the local switch.

       o  STATUS:  Status of the local point code.  State will be
          AVAILABLE or UNAVAILABLE.

       o  SUBSYSTEM NUMBER AND STATUS:  Subsystem number and status
          information are derived via normal subsystem allowed (SSA)
          and subsystem prohibited (SSP) network management messages.
          Status is indicated by backlighting colors as follows:

            -- Allowed:  Green background with black lettering

            -- Prohibited:  Red background with white lettering

            -- Unequipped:  Yellow background with red lettering.

     Figure .AW G376/ shows an example of the 1523 page.  In this example,
     subsystem 246 is backlighted.  Its status is determined by
     coloration of the backlighting.

     There are no commands on the 1523 page.
     The purpose of Page 1940 is to provide a simplified procedure
     for installing Broadcast Warning Messages (BWM) into the 5ESS
     switch.  The EASY BWM feature simplifies the BWM application
     process by freeing the user from entering commands and
     constantly having to monitor the progress of the BWM.
     The Easy BWM Installation page can be used to back out, install,
     or apply BWMs with a single command. The page also provides
     control of the soak interval timer. This user specified time
     will override the 24-hour default value.

     Several terms used in the commands which may be confusing are
     described as follows:

       o  Install:  To take an official BWM from the start command to
          the official command. The TEMP BWMs cannot be made
          official.

       o  Back Out:  To take a TEMP or craft BWM that is soaking and
          back it out of the system.

       o  Apply:  To take a TEMP or craft BWM from the start command
          to the soak command.

       o  Soak:  To leave a BWM in the system for a certain period of
          time so as to allow the update to have a chance to interact
          with other pieces of software in the system.

       o  Official:  To make a BWM permanent in the system.

     The 1940 page (Figure .AW G377/) is divided into two basic areas,
     upper and lower. The upper area of the page contains the poke
     commands used to control the BWM processes.  (The poke commands
     are discussed in the ``Commands'' section, following.)  The
     lower area of the page provides a response indicating the
     progress of a BWM procedure or a summary of an error message if
     an error occurs during the execution of a command.  Also found
     in the bottom area are the names of the Install, Back Out, and
     Apply BWMs in addition to the value of the BWM Soak Interval
     Timer.

     Whenever Page 1940 is displayed, the values for Install BWM
     Name, Back Out BWM Name, Apply BWM Name, and BWM Soak Interval
     Timer will be populated with default information.  The following
     describes each of these fields in detail.

     The Install BWM Name is the name of the BWM that should be
     inputed into the switch. The Install BWM Name can be changed
     with the 9810 poke command.

     The Back Out BWM Name is the name of the TEMP/craft BWM to be
     backed out before the next BWM is to be installed/applied.  If
     no BWM is in the soak state, the default value NONE will be
     displayed. To change the name of the BWM to be backed out, use
     the 9820 poke command.

     The Apply BWM Name is the name of the TEMP/craft BWM to be
     applied after the Install BWM is in the official state. This
     field always defaults to the value NONE. To change the name of
     the BWM to be applied, use the 9830 poke command.

     The BWM Soak Interval Timer is defaulted to 24 hours 00 minutes.
     This field will always be displayed. If the value needs to be
     changed, use the 9840 poke command.

     The middle of Page 1940 provides commands used to process BWMs.
     These commands are as follows:

     CMD              RESULT

     9800             Start Execution
     9810,(Y)         Change Install BWM Name
     9820,(Y)         Change Back Out BWM Name
     9830,(Y)         Change Apply BWM Name
     9840,HH,MM       Change BWM Soak Interval Timer
     9850,F           Dump Inst BWM File
     9860             Stop Execution
     9870             Stop After Soak

     The 9800 poke command starts the execution of the EASY BWM
     process. If the back out BWM is populated with a BWM name, it
     backs out that BWM, then it installs the install BWM, and if
     appropriate, applies the apply BWM. This poke command must not
     be entered before the install BWM name is populated (9810 poke
     command) with a valid BWM name.

     After execution is started on the 1940 page and its response
     line states that EASY BWM IS IN PROGRESS, the page is not
     updated until it completes successfully or runs into a failure.
     To find out the current status of BWMs look on Page 1960. The
     1960 page is kept up to date while the EASY BWM process is
     executing.

     The 9810 poke command populates the Install BWM Name. This BWM
     is the one which will be used as the install BWM. This field can
     contain any valid 6- or 10-character BWM name. This field MUST
     be populated for the EASY BWM process to work. If this BWM name
     is a TEMP BWM, then this BWM will not be made official and the
     Apply BWM will NOT be applied to the 5ESS switch.

     The 9810 poke command should always be the first poke command
     entered on the page. This is needed since this poke command
     initializes the page with default information, except for the
     data just entered. If the page is set up and this is the last
     poke command executed, the page will be initialized and the
     previous input will have to be reentered.

     The 9820 poke command will populate the Back Out BWM Name. This
     BWM is the one which will be backed out of the 5ESS switch when
     execution is started. This field is populated for the user and
     should never have to be changed by the user. This field can
     contain all valid BWM names except official BWMs (BWMs that
     start with BWM).

     The 9830 poke command will populate the Apply BWM Name. This BWM
     is the one that will be applied after the Install BWM is
     finished. This will NOT happen if the Install BWM is a TEMP BWM.
     In that case, the Apply BWM will NOT be applied to the 5ESS
     switch.  This field can contain all valid BWM names except
     official BWMs (BWMs that start with BWM).

     The 9840 poke command will allow the user to change the soak
     interval timer for the Install BWM.  Default value for the timer
     is 24 hours and 00 minutes.  The timer does not change until the
     soak section has been executed and the timer set.  At that time
     the EASY BWM process resets the soak interval timer to the value
     the user entered.

     The 9850 poke command will print (on the ROP) any American
     standard code for information interchange (ASCII) file
     associated with the Install BWM. This includes the MSGS and
     SCANS files.  To print the MSGS file for the Install BWM with
     this command, you would enter 9850,MSGS.

     The 9860 poke command will stop the execution of all commands on
     Page 1940 (see example outlined as follows). Execution will be
     stopped only after the current step in the current state is
     completed. This command is the same as the 9560 poke command on
     Page 1960.

     The 9870 poke command allows the user to stop the execution of
     the EASY BWM process after the Install BWM has started its soak
     section.  If this option is selected, the 9870 poke must have
     been entered causing the STOP AFTER SOAK status field to show
     ON, and the execution of EASY BWM will stop awaiting user input.
     To restart the EASY BWM process, reenter the 9800 poke. If the
     9870 poke was not entered, the STOP AFTER SOAK status field will
     show OFF, and the  EASY BWM process will not stop until
     execution has completed in full.  Note that the 9870 poke
     toggles the STOP AFTER SOAK option, so that if it was ON,
     entering the 9870 poke will cause it to turn OFF.  Also, if it
     was OFF, entering the 9870 poke will cause it to turn ON.

     An example using the 1940 page follows.  For this example,
     assume:

       o  TEMP BWM TMP88-6082 is soaking.

       o  Official BWM BWM88-0050 is to be installed.

       o  TEMP BWM TMP88-6089 is to be applied after the install BWM
          has finished.

       o  A soak time of 2 hours and 0 minutes is wanted for the
          Install BWM.

     The following is a list of steps that the user would take to
     accomplish this example:

                     ACTION                                  RESULT

   1.  Enter the 1940 poke command.          The 1940 page is displayed.
                                             The Back Out BWM field is
                                             populuated with TMP88-6082,
                                             the rest of the page contains
                                             default information.

   2.  Enter the 9810,880050 poke command.   The Install BWM field is
                                             populated with BWM88-0050.

   3.  Enter the 9830,886089 poke command.   The Apply BWM field is
                                             populated with TMP88-6089.

   4.  Enter the 9840,2,0 poke command.      This will populate the soak
                                             interval timer with 2-00.

   5.  Enter the 9800 poke command.          This will start execution of
                                             the EASY BWM process.

     The purpose of the 1941 page is to provide a simplified
     procedure to schedule BWM for automatic installation into the
     5ESS switch.  The BWM automation feature simplifies the BWM
     installation process by allowing the user to schedule a BWM to
     be automatically installed at a later date and time, thus
     freeing the user from entering commands and constantly
     monitoring progress of the BWM.
     The BWM Automation Scheduling page can be used to perform the
     following:

       o  Schedule or reschedule (start time, start date, and/or
          install state) a BWM for automatic installation

       o  Resume a stopped automatic installation

       o  Toggle BWM automation ON (allowed) or OFF (inhibited)

       o  Execute an office healthcheck

       o  Query BWM automation status

       o  Show the results of the last office healthcheck

       o  Cancel the current BWM scheduled.

     The 1941 page is divided into three areas.  The area at the top
     of the page contains the poke commands used to control BWM
     automation process.  The area in the middle of the page shows
     the current scheduled BWM name, the date and time the BWM is
     scheduled to be installed, the installation state (VERIFY, SOAK,
     or OFFICIAL), the current BWM automation status (ALLOWED or
     INHIBITED), and the date, time, and status of the last office
     healthcheck.  The area at the bottom of the page provides
     responses indicating the progress of the BWM automation
     procedures.

     The following describes each of these fields in detail:

       o  BWM SCHEDULED:  Name of BWM currently scheduled for
          automatic installation, or NONE.

       o  STATE:  Current state of automation, for example, IDLE,
          SCHEDULED DATE/TIME, STOPPED, IN PROGRESS, etc.

       o  BWM INSTALL STATE:  Application stage that currently
          scheduled BWM will be installed to.  Application stages are
          verify (VFY), soak (SOAK), or official (OFC).

       o  BWM AUTOMATION:  Current status [on (ALLOWED) or off
          (INHIBITED)].  If BWM Automation is inhibited, BWMs cannot
          be scheduled for automatic installation.

       o  LAST HEALTHCHECK STATUS:  Date and time that the last
          office healthcheck was run and its result, or it will
          indicate that a healthcheck is currently in progress.

       o  RESPONSE:  Information relative to BWM automation activity.

     Figure .AW G378/ shows that BWM93-0001 is scheduled to be installed
     officially on 10/15/93 starting at 19:30.  The BWM automation is
     allowed, and the status of the last healthcheck (run on 10/12/93
     15:46) is PASSED.

         CMD       RESULT

       9920,X      Schedules a BWM for automatic installation. The BWM
                   name specified will be scheduled for automatic
                   installation. The start day, time, and install state
                   will be derived from the default values listed in the
                   BWM Automation Office Profile (see Page 1942).  Note
                   that for the start date/time, the BWM will be scheduled
                   for the very next time slot that is NOT off, as listed
                   in the office profile.  After this command is
                   successfully accepted, the indicators which show the
                   current BWM name, start day/time, and install state
                   will be updated accordingly.
       9921,X      Reschedules a BWM name for automatic installation.  This
                   command is used when a scheduled BWM name needs to
                   be changed.  This command will only modify the BWM name,
                   not the start day, time, or install state.
     9922,MMDDYY   Reschedules the start date for automatic BWM
                   installation.  This command is used when the start date
                   of a scheduled BWM needs to be changed.  The valid
                   argument is MMDDYY, where MM is a 2-digit month (01-12),
                   DD is a 2-digit day (01-31), and YY is a 2-digit year
                   (00-99).
      9923,HHMM    Reschedules the start time for automatic installation.
                   This command is used when the start time of a
                   scheduled BWM needs to be changed.
       9924,Z      Reschedules the install state for automatic installation.
                   This command is used when install state for a scheduled
                   BWM needs to be changed.  The valid install states are
                   VFY (verify), SOAK, and OFC (official).
        9925       Resumes an automatic BWM installation that was previously
                   stopped or aborted.
        9926       Inhibits (turns off) BWM automation.  A BWM cannot be
                   scheduled for automatic installation when
                   BWM automation is INHIBITED.
        9927       Allows (turns on) BWM automation.  A BWM can be
                   scheduled for automatic installation only when
                   BWM automation is ALLOWED.
        9928       Requests that an office healthcheck be executed.
                   The final result (PASSED or FAILED) will show on
                   this page, while the detailed results of this command
                   will be sent to the ROP.
        9929       Reports the status of BWM automation (ALLOWED or
                   INHIBITED), and the reason for it being inhibited, if a
                   reason exists.
        9930       Reports to the ROP the detailed results of the last
                   healthcheck that was run.
        9931       Cancels a BWM that is currently SCHEDULED for automatic
                   installing but has not yet started installation.

     The purpose of the 1942 page is to provide current status and a
     simplified procedure for modifying the BWM automation office
     profile. The office profile is used when scheduling a BWM for
     automatic installation, when executing an office healthcheck,
     and when determining if the Customer Service Computer Access
     Network System (CSCANS) is allowed to update the BWM Automation
     Office Profile.
     The 1942 page lists all valid fields of the office profile for
     BWM automation except for the BWM automation healthcheck
     conditions which are listed on Page 1943.  It shows the value
     that is currently set up for each field and provides the
     commands to reset the value.

     At the bottom of the page, the result for each command request
     is displayed.

     Figure .AW G379/ is an example of the 1942 page showing an office
     profile.

 2
     CMD                   RESULT

     9901,{VFY|SOAK|OFC}   Modifies the default BWM automation install
                           state.
     9902,HHMM             Modifies the default soak time (HH = hours;
                           MM = minutes) that will be used during the soak
                           stage of a BWM that is automatically installed.
     9903,{MAJOR|MINOR}    Modifies the alarm level that will be used when
                           an office alarm is fired during a BWM automation
                           process.  The valid values are MAJOR and MINOR.
     9904,{Y|N}            Modifies the CSCANS control field.  "Y"
                           indicates that CSCANS is allowed to send
                           commands to modify this office profile.
                           "N" means CSCANS is not allowed to send
                           commands to modify this profile.
     9905,HHMM             Before BWM automation starts, a warning message
                           is printed to the ROP to inform office personnel.
                           This command sets the amount of time prior to
                           starting BWM automation to send this warning
                           message out.
     9906,HH               During the execution of a healthcheck, the
                           elapsed time since the last processor (AM, SM,
                           or CMP) initialization is checked.  When the
                           elapsed time is greater than the time set up
                           in this field, the healthcheck will PASS.  This
                           command is used to reset a desired elapsed time.
     9907,{Y|N}            Indicates whether a BWM should be automatically
                           cleared (CLR:BWM) after it is automatically
                           installed and made official.  If set to ``Y'',
                           the BWM will be cleared; if set to ``N'', it
                           will not.
     9908,HHMM,HHMM        Modifies the time interval that BWM automation
                           will  not be scheduled for, by default, on
                           Sunday.
     9909,HHMM,HHMM        Modifies the time interval that BWM automation
                           will not be scheduled for, by default, on Monday.
     9910,HHMM,HHMM        Modifies the time interval that BWM automation
                           will not be scheduled for, by default, on
                           Tuesday.
     9911,HHMM,HHMM        Modifies the time interval that BWM automation
                           will not be scheduled for, by default, on
                           Wednesday.
     9912,HHMM,HHMM        Modifies the time interval that BWM automation
                           will not be scheduled for, by default, on
                           Thursday.
     9913,HHMM,HHMM        Modifies the time interval that BWM automation
                           will not be scheduled for, by default, on Friday.
     9914,HHMM,HHMM        Modifies the time interval that BWM automation
                           will not be scheduled for, by default, on
                           Saturday.

     The purpose of the 1943 page is to provide a simplified
     procedure for setting (turning ON) and clearing (turning OFF) 25
     predefined BWM automation healthcheck conditions.  This page
     also provides help commands to request further information on a
     given condition.
     The 1943 page allows users to set or clear each BWM automation
     healthcheck condition by using the 4XX and 5XX commands,
     respectively.  Detailed information explaining each condition
     can be retrieved via the 9XX help command.  Conditions that are
     SET on this page are checked during an office healthcheck.  Each
     SET condition is backlighted on the display.  The result of each
     SET or CLR request is show on the bottom of the page in the
     RESPONSE area.

     Each of the 25 predefined conditions is described in the
     following listing.
 2
     NUMBER (XX=)   CONDITION         DESCRIPTION

          00        AM OVERLOAD       AM in overload
          01        SM OVERLOAD       SM(s) in overload
          02        CMP OVERLOAD      CMP(s) in overload
          03        SM HASHERR        SM(s) in hashsum error
          04        CMP HASHERR       CMP(s) in hashsum error
          05        SM ISOLATED       SM(s) in isolation
          06        AM BREAKPOINTS    Breakpoints in the AM
          07        SM BREAKPOINTS    Breakpoints in the SM(s)
          08        CMP BREAKPOINTS   Breakpoints in the CMP(s)
          09        LAST AM INIT      Time of last AM initialization
          10        LAST SM INIT      Time of last SM initialization
          11        LAST CMP INIT     Time of last CMP initialization
          12        AM SIMPLEX        AM in simplex mode
          13        RC INHIBIT        Recent change inhibited
          14        DBREORG INHIBIT   Automatic data base reorganization
                                      inhibited
          15        CORCS INHIBIT     CORCs inhibited
          16        RETR  GNUPD LTG   Retrofit, software release update,
                                      or large terminal growth in progress
          17        ODD BACKUP        ODD backup in progress
          18        RC IN PROGRESS    Recent change in progress
          19        GEN BACKUP        GEN backup in progress
          20        BWM IS TEMP       Temporary BWM updates on switch
          21        BWM INCONSISTNT   BWM inconsistencies
          22        PERIPHERALS       Are there an insufficient number of
                                      peripheral units such that automatic
                                      application of the SU would not be
                                      successful
          23        SCC LINK          Is SCC link active
          24        FILESPACE         Is there enough file space for BWM to be
                                      installed; only run when a health-
                                      check is done as part of an automated
                                      BWM installation.

     Figure .AW G380/ shows an example of the 1943 page.  In this example,
     all conditions except 09 and 15 are SET and will be checked
     during the office healthcheck.
     The commands provided on this page are as follows (where XX = 00
     - 24):

     CMD   RESULT

     4XX   Sets healthcheck condition XX (turns it ON).
     5XX   Clears healthcheck condition XX (turns it OFF).
     9XX   Requests further information on healthcheck condition XX.

     Copyright(c) 1994 AT&T
     All Rights Reserved

     This material is protected by the copyright laws of the United
     States and other countries.  It may not be reproduced,
     distributed or altered in any fashion by any entity, including
     other AT&T Business Units or Divisions, without the expressed
     written consent of the Customer Education & Training
     Organization.

     For permission to reproduce or distribute please contact:

          5ESS(R) Switch and 5ESS(R)-2000 Switch
          Documentation Product Development Manager
          1-800-334-0404

     Notice

     Every effort was made to ensure that the information was
     complete and accurate at the time of development.  However
     information is subject to change.

     Trademarks

       Note:   The following letters enclosed in parentheses are
               used to mark the first representation of trademarks
               or service marks in this data base.

                       (R)   = Registered trademark
                      (TM)   = Trademark
                      (SM)   = Service mark.

     The following is a list of trademarks used throughout this data
     base:

                   5ESS -- Registered trademark of AT&T.
                    ESS -- Trademark of AT&T.
                   ANSI -- Registered trademark of American National
                           Standards Institute.
               AUTOPLEX -- Registered trademark of AT&T.
                  INTEL -- Registered trademark of INTEL Corporation.
               KEYSTONE -- Registered trademark of Laser Magnetic Storage
                           International Company.
               MOTOROLA -- Registered trademark of Motorola, Inc.
                    SLC -- Registered trademark of AT&T.
               TELETYPE -- Registered trademark of AT&T.
                   UNIX -- Registered trademark of UNIX System
                           Laboratories, Inc.

     Ordering Information

     The Ordering number for this document is AT&T 235-105-110.
     To order this document, call the AT&T Customer Information Center
     in Indianapolis, Indiana, on 1-800-432-6600.  Refer to
     AT&T 235-001-001, Documentation Description and Ordering Guide
     for additional ordering information.

     Orders may also be called in on 1-800-432-6600 or faxed in on
     1-317-322-6484.

     Support Telephone Number

     AT&T provides a telephone number for you to use to report errors
     or to ask questions about the information in this document.  The
     Documentation HOTLINE telephone number is:

                              1-800-334-0404

     and it is available from 7:30 a.m. to 4:30 p.m. Eastern time
     (within North Carolina, dial 1-910-727-6681).  Outside of those
     hours, the line is served by an answering machine.

     Developed by the AT&T Network Systems Customer Education
     & Training.